Merge Node Behavior Change?

Questions
, ,
1

Self Hosting n8n moved from version 1.69.2 and 1.70.1 to 1.71.2 and 1.76.1
In 1.69.2 and 1.70.1 my merge node would return No output data returned if the if node filtered out data going to input 1 of the node. I have workflows that are not working now in version 1.71.2 and 1.76.1. Is this a planned behavior change? Which versions have the bug? I already know I can change the if node to always output data, but I want to verify the old behavior is the bug first before changing my workflows.

1.69.2 and 1.70.1

image
image1024×449 37.3 KB

1.71.2 and 1.76.1
image
image942×550 48.9 KB

2

It looks like your topic is missing some important information. Could you provide the following if applicable.

  • n8n version:
  • Database (default: SQLite):
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app):
  • Operating system:
3
  • **n8n version: 1.70.1 to 1.71.2
  • **Database (default: SQLite): SQLite
  • **n8n EXECUTIONS_PROCESS setting (default: own, main): own
  • **Running n8n via (Docker, npm, n8n cloud, desktop app): Docker
  • **Operating system: Ubuntu 22.04
4

Can you please share the workflow. Preferably with some sample data we can test it with.

1 Like
5

Sorry for the late reply. The workflow above has different behavior based on which version of n8n I am running. The set nodes create the data that will cause the difference in behavior. In 1.70.1, the merge node will not fail only receiving data in input 2. It will just stop that path in the workflow. In 1.71.1, the merge node will fail because no data was received in input 1. I am assuming this is how it is supposed to behave, but that means refactoring some of my workflows.

6

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