Process Calling 3rd party API

RE: Process Calling 3rd party API

Radhamani Ramasamy — Mon, 06 Apr 2026 10:54:25 GMT

Thank you for the suggestions!

The reason we kept it synchronous is to regulate number of API's being made at the same time. If we make it async, then many concurrent calls may happen and also many concurrent instances might get created in system. So I went with synchronous (Delete completed instances).

Yeah, I am also going to suggest making the scheduler 2 hour once to client.

Earlier this MNI was present as a single expression rule inside which API is being called in foreach. The rule was being called from script task. Which was triggering long running work in backend. After which this is changed as MNI with 250 batch which has created memory spike & CPU utilization. Now reduced batch size to 50. We need to monitor the CPU for a while to see whether the memory became stable.

I have also made sure this job doesn't overlap with other Scheduler's timing in Production to make sure system resource is not getting overloaded with multiple items at the same time

RE: Process Calling 3rd party API

Radhamani Ramasamy — Mon, 06 Apr 2026 10:48:28 GMT

We also write some additional data into Maria DB to the table. Only few columns in table need to be synced from external system. So we can't make it synced I guess

RE: Process Calling 3rd party API

Shubham Aware — Mon, 06 Apr 2026 10:08:07 GMT

Many environments have similar legacy schedulers - full revamps cost extra effort.
My Suggestion, Try running sub-processes asynchronously for engine balancing and reduce frequency if possible (e.g., 2-hourly). If it still flags, open a support ticket to suppress this health check point as a known design issue; Appian can whitelist it so it won't flag future runs. Health checks guide best practices, but exceptions exist for valid legacy cases.

RE: Process Calling 3rd party API

Stefan Helzle — Mon, 06 Apr 2026 08:56:04 GMT

The health check notifies you of a problematic design decision. You can either ignore it and manage the risk, or change the design. This is really up to you.

Would it be possible to go with a synced record approach?