Workato 'Wait for async calls to complete' action getting stuck in processing

[dawidleman]

Hi,

Recently we've encountered strange Workato behavior. In a loop, we're calling recipe functions asynchronously, store the job references in a list and outside of the loop we pass that list to the "Wait for async calls to complete" action. We want the recipe to wait for all the child jobs to complete and continue parent processing when all finished.

The weird behavior is that even when all the jobs completed, the parent recipe job is stuck in processing state:

Here's the implementation in the parent process:

What's even more interesting is that if we set the timeout limit to e.g. 1min (line in example) and wait it out, the parent process is still stuck in processing. Here's the screenshot from yesterday right after I canceled the execution (look at the duration time):

That's definitely a 1min timeout not working.

Does anyone had similar issues and came up with a solution for that?

Thanks  

[rajeshjanapati]

Hi @gprao13,

Repeat Job in Workato allows you to re-run a previously executed job using the same trigger data that was processed earlier. It performs all the recipe actions again based on the data from that job, without fetching new data from the source application.

For example, suppose you tested a recipe earlier and later modified the recipe (say, updated the second step) and saved it.
If you now repeat that previously tested job, Workato will run the latest saved version of the recipe — not the older version that was used.

---

💡 Why use Repeat Job?

In real-time integrations, we usually receive data from source applications. When testing or debugging a recipe, it’s not best practice to request the source system to resend the same data repeatedly.

In such cases, the Repeat Job feature is very useful — it lets you reuse the same trigger data from a previous job and re-run the workflow through all subsequent steps. This helps in:

• Troubleshooting failed jobs

• Testing modifications without triggering new data

• Validating mapping or logic changes

• Ensuring end-to-end success after fixing errors

hope you got some clarity, if not please let me know, will discuss further.

Thanks,

J Rajesh Kumar.

[girish-naralla]

If your recipe includes long-running actions, it’s essential that the recipe is in an active state when you attempt to repeat a previous job. Repeating a job while the recipe is inactive can lead to the same error or failure that occurred during testing.

[brettsherwood]

From the docs: https://docs.workato.com/en/recipes/testing.html
---
CANNOT RUN LONG ACTIONS IN TEST MODE

Long actions require dedicated workers to periodically check if the action is complete. This is not available in test mode. Testing a recipe that contains a long action may cause the job to stall in the Processing status.
---

Can definitely be frustrating at times to deal with...