Merge Nodes causing non-initiated nodes to activate

[MutedJam]

Hi @pb84, this is the expected behaviour I am afraid. The Merge node will pull in data from connected input branches nodes, even if these branches wouldn’t normally run.

In your example the solution is simple though, simply don’t use a merge node.

With the Merge node, the top branch will run:

Without it the top branch won’t run and you would only get one item on your final node:

I know this is confusing and can make things more complicated, so please accept my apologies for the inconvenience this causes.

You might want to leave a vote on this feature request to have this changed in the future:

Merge node suggestion: add option to disable triggering of previous nodes

The idea is: The Merge node has a unique behavior in which it activates connected nodes independently (please also add an explanation in the documentation here: Merge | Docs). I think it’s something that should be configurable in the node. My use case: I had multiple cases in which the Merge node triggered nodes that were not supposed to be triggered (usually in an unused path of an IF node). I think it would be beneficial to add this because: It gives more control of the Merge node, in …