When executing workflow not all nodes become triggered

I have a workflow with many parallel paths that I want to merge back.

When executing the workflow it is reporting error:

Problem in node ‘merge everything back1‘
Node ‘Aggregate2’ hasn’t been executed [line 2]

The problem is that the merge node is expecting 2 inputs but it is only receiving one input.

Here above the status after clicking on “Execute workflow”.

What I do not understand why did “extract revisions” node not output 1 item as it has received 1 item.
If I open that node I see that no Output has been generated but when I click on “Execute step” it is producing output as expected. If I pin that output then the problem is that the next node after the pinned node is not producing any output when executing the workflow.

So it seems that n8n has a problem properly executing my workflow with parallel flows.

The issue is clear, the node code node called merge everything back1 has executed before the extract revisions node and threw an error. So the agent called extract revisions would’ve worked if the execution didn’t stop.

This is the point of the merge node, though. If you use a merge node instead of merge everything back1 the workflow wouldn’t have stopped, and would’ve waited for all nodes to execute.

2 Likes