Hello automators! I stumbled upon a strange behavior today. My workflow has a scheduled trigger every day at 23:55. I won’t go through all the details, the point is this last IF node outputs 14 items, they are parsed to the loop and the loop then processes 1 item at a time (Batch Size = 1). The node which runs the subworkflow is set to “Run once for each item” and also the option “Wait For Sub-workflow Completion” is turned on. So once the sub-workflow completes, it loops through the next item and triggers the sub-workflow again.
There are no errors or anything, it’s just that it processed 6 items and stopped. I even checked the sub-workflow executions - only 6 executions, no errors.
There is no timeout set for the workflow.
Does anyone have any suggestions?
1 Like
Hey @Velislav_Ivanov From your screenshot, it looks like 14 items enter the loop, but execution stops after 6 even though “Run once for each item” + “Wait for completion” are on. A couple of ideas:
-
Check if the main workflow execution itself is being cut short (server timeout, memory, or execution settings like EXECUTIONS_TIMEOUT / EXECUTIONS_PROCESS). Even if you didn’t set one manually, global limits might apply.
-
Try enabling “Always Output Data” on the Loop node to confirm whether items #7+ are reaching it at all.
-
If possible, add a dummy Set node after the Loop to log all processed items — that’ll confirm if the stop happens inside the loop or at the subworkflow call.
2 Likes
Thanks, i’ve turned on Always output data and will see how it goes tomrrow.
As per @Aashu_Rajput comment to enable Always Output Data, you actually need to set that on the Call Workflow node. My suspicion is that your 6th record’s sub-workflow call is returning nothing back to the main call or erroring out maybe which could cause the workflow to end there. I might be wrong not knowing exactly what your sub workflow actually does
yup, I’ve turned on the “Always output data” on the node which calls the sub-workflow. Also made sure the sub-workflow actually returns data every time it finishes.
Once it runs tonight I will know if this was the case.
1 Like
If not then please share your workflows in a code block so we can have a look
It worked fine now, so this was the cause. Thank you!
Ok great! Please mark the correct answer as the solution to help others
