Handling Long-Running Asynchronous Child Recipes and 24-Hour Wait Timeout Limit Solutions
Hi Everyone, I'm looking for some guidance on a use case involving asynchronous child recipes. In my parent recipe, I invoke a child recipes asynchronously multiple times for paralled processing. For each async call, I store its job reference ID in a list. Later in the recipe, I use the "Wait for async calls to complete" action, passing the list of job reference IDs so that the parent waits until all child recipes have finished. The challenge is that some of these async calls are taking a very long time to complete. The "Wait for async calls to complete" action has a maximum timeout of 24 hours. One or more async calls are still running after this timeout, the wait action times out and the parent recipe continues its execution. As a result:
Some child recipe jobs are still in the Processing state.
The parent recipe proceeds with downstream steps, even though not all child recipes have completed.
This leads to downstream processing starting before all required child recipe processing has finished, causing inconsistencies. Has anyone faced a similar scenario? I'm looking for recommendations or best practices for handling long-running asynchronous child recipe calls. Specifically:
Is there any workaround to wait beyond the 24-hour limit?
Is there a recommended design pattern for coordinating very long-running async recipes?
