`Merge` node makes previous nodes executed `Not` as expected

Questions
1

Describe the issue/error/question

I found Merge node can cause some branches be forced executed, even they have no input data.
Is this behavior as expected?

n8n1
n8n11356×655 15.2 KB

n8n2
n8n21526×798 19.2 KB

n8n3
n8n31027×696 11.2 KB

What is the error message (if any)?

No

Please share the workflow

Share the output returned by the last node

Information on your n8n setup

  • n8n version: 0.201.0
  • Database you’re using (default: SQLite): MySQL
  • Running n8n with the execution process [own(default), main]: own
  • Running n8n via [Docker, npm, n8n.cloud, desktop app]: Self-Hosted

Thanks for any Reply~~

2

Hi @helayzhang, welcome to the community!

The Merge node can indeed force previous nodes to run even if they wouldn’t normally do so. This is expected and explained here for example (and there are also a number of other posts of folks caught off guard by this).

To avoid such trouble with the Merge node you might want to consider building sequential flows like suggested here instead.

3

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.