RE: Asynchronous API call from interface and follow up API to get the status of the job.

khushim2428 — Tue, 21 Jul 2026 12:10:41 GMT

Your approach is technically feasible, but the deciding factor is how long the external job typically takes.

If the job usually completes within a few seconds, I'd consider polling the status API directly from the interface (using a refresh variable or refresh interval) until the job completes or a timeout is reached. This avoids introducing another process model solely for polling.

If the external job can take longer (tens of seconds or minutes), then using a separate process model is more appropriate. However, I'd be cautious about relying on activity chaining for a long-running asynchronous operation, since activity chaining is intended for short-lived interactions and may not be reliable for extended polling.

Your proposed approach of starting a process and monitoring it via Query Process Analytics can work, but it does add complexity and requires handling retries, maximum wait times, failures, and process timeouts.

Out of curiosity, how long does the external job usually take to complete? That will largely determine the most suitable design.