Again Merge Node triggers unwanted second branch of IF statement (I use latest cloud version of [email protected])

[Randall]

Describe the problem/error/question

When I try to execute IF mode logic I get the same unwanted execution of the second branch by Merge node, when in production mode!!! This is perfectly described in this thread:

Unexpected behavior from unvisited nodes in a Switch-and-Merge workflow

I have a set of items that I want to process conditionally, and tried using a switch-and-merge pattern (using the Append mode) to do this. When the switch node outputs at least one item of each branch, the merge node behaves as expected. But when the Switch node outputs no items of some branch, the nodes in the unvisited branch still run. Here is a minimal example: [Screenshot 2022-01-01 at 2.19.58 PM] Output returned by the last node [ { "Type": "A", "x": 1 },…

When in debug mode, it works as expected (does not trigger second IF branch).

And this is latest ([email protected]) version of cloud n8n!

Any ideas how to fix this ASAP? Is there any way for n8n to fix this returned bug ASAP?

My task is the following:

I need to execute sub-process for 1 or many items.

If processing node returns “result”: “OK” I process item in one If branch, otherwise I process it differently in another If branch.

Merge is used at the end to collect all inputs before sub workflow exists.

Currently Merge works correctly ONLY for use case with many input items and when OK and Non OK are present in the output (both IF node branches are executed at least once).

Merge triggers unwanted second IF node branch, in case I got one input item, or all input items receive processing result OK or all of them receive Non OK (basically when ONLY single IF node branch was used)…

[jabbson]

Would you like to post a short repro of this issue?