I have a workflow that calls another workflow that creates tasks. We have two paths in the task creation workflow: one creates an individual task using the "Catalog Task" action and the other creates a dynamic number of tasks using a "Run Script" action. Because the Run Script doesn't have the same "wait for task" functionality as the Catalog Task action, I have a condition to check if all tasks closed; if they aren't, it then waits. For testing, the wait is only 1 minute but in the future this will be increased. What I'm finding is that something is causing the wait for the child workflow to cancel only when it follows the run script path, after about an hour of waiting.
This shows the child workflow is still waiting and hasn't moved to end:
This shows that the parent workflow has moved beyond the workflow step to the next Set Values step:
Does anyone know what might be causing this issue?
Hi Kristen,
Are there a lot of activities in the subflow? Is it possible that you are hitting the 'max activity count' since your "If" + "Timer" loop would be at 120 activity counts if it goes for 60min times two activities. If you hit that count it will cancel the workflow out.
Hi Kristen,
Are there a lot of activities in the subflow? Is it possible that you are hitting the 'max activity count' since your "If" + "Timer" loop would be at 120 activity counts if it goes for 60min times two activities. If you hit that count it will cancel the workflow out.
