Describe the problem/error/question
I have a result from a webhook that is defided by an if node… On the true node I have multiple nodes connected. I have this pattern on more locations within my workflow. The issue is that all transition contain 1 item, but only the top node gets executed and follows the flow through.
How do I make it so that all sub-nodes are executed? If even possible.
What is the error message (if any)?
Please share your workflow
Share the output returned by the last node
Information on your n8n setup
- n8n version: 1.79.0
- Database (default: SQLite): POSTGRES
- n8n EXECUTIONS_PROCESS setting (default: own, main): own
- Running n8n via (Docker, npm, n8n cloud, desktop app): Docker
- Operating system: Mac M1
Hello!
I actually tried to replicate your workflows but all my branches run. However a simple way that might fix your problem is use a merge node in the end of your flow with the “Wait for All Inputs to Arrive” setting and link all your branches to it.
2 Likes
Hi @VikingFox,
Welcome to the community!
I tested the exact same version of n8n deployed on docker an it is working for me: (the only difference is that I set it up with SQLite)
It is also consistent with this statement of the official documentation:
For workflows created in version 1.0 and above: executes each branch in turn, completing one branch before starting another. n8n orders the branches based on their position on the canvas, from topmost to bottommost. If two branches are at the same height, the leftmost branch executes first.
Maybe it’s a good idea to enable more logging and checking if the workflow is throwing any errors.
Merging the data did the trick…Funny enough if you choose the append function, you are not able to get the data from the Merge node as $json.[attribute] or $(“node”).first().json.[attribute]. But I can now get them from the nodes just before the merge, and that is all that I needed.
2 Likes
Logging is a paid feature undfortunatly.
But your comment made me think about the gathering of the nodes, and that was an edit field node. This node did not complete, because the next node could not function before all data was present, so it broke the flow… that is why the next node down, did not axecute. I fixed this with the merge node.
1 Like
