Describe the problem/error/question
In our system, we use multible subworkflows chained together. One of these subworkflows for some reason always executes the next workflow 5 times sometimes, sometimes just once, even though it just receives one item and is set to only execute the next once.
Please share your workflow
Information on your n8n setup
- n8n version: 1.123.22
- Database (default: SQLite): SQLite
- n8n EXECUTIONS_PROCESS setting (default: own, main): own
- Running n8n via (Docker, npm, n8n cloud, desktop app): n8n cloud
- Operating system: MacOS
1 Like
The issues is that you have set waitForSubWorkflow: false. Set it to true instead.
If you have upstream changes or feed back to the beginning of the chain it stacks multiple executions before the previous one finished
Hi @MoritzSchoelderle I think your setup really prevents that node from being executed more than 1 time, but as you are saying that it still executes more than one time sounds like a problem, consider upgrading to the latest 2.x.x version and that would should solve the issue.
But doesn’t that mean that the node workflow will stay running until all subworkflows are finished. That’s a problem for us because that workflow then blocks one execution that we might need for another run.
yeah the async stuff queues up if you’ve got loops or retry logic upstream — thats why youre getting multiple executions. waitForSubWorkflow: true stops the queueing but blocks the slot like you said.
could try a merge node after the execute workflow to wait for the result without blocking the next iteration. or check if youve got fan-out logic upstream (like looping over items) thats calling the node multiple times per execution
