Strange behavior of merge node

Questions
,
1

Describe the problem/error/question

Hey everyone
I have a strange behavior of the merge node. When I run the workflow below, it runs 4 times as it should. But the merge node works just two times. After that, it doesn’t output any data, if the filter is set on the item on the second run. If I change the order of the parallel nodes, it gives back more or less items. Has anyone an idea, why this is happening and how to avoid that?

Filter set to the second run

grafik
grafik1148×557 52.7 KB

Filter set to fourth run

grafik
grafik1116×573 51.4 KB

What is the error message (if any)?

Please share your workflow

Share the output returned by the last node

Information on your n8n setup

  • n8n version: latest
  • Database (default: SQLite): default
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app): Docker
  • Operating system: Linux
2

could you please elaborate what you are trying to achieve with the workflow?

3

I have different csv files, which structure is always the same, but I load them with different parameters, which change inidividually. These parameters are in the set nodes 1 to 4, so that the workflow can be same, but with different variables. In the end, the modified csv-File are written back to harddrive. Works for my other workflows very good, just here the merge node messes it up.

4

Does anyone know if this is a bug?

5

Not solved yet

7

Is this somehow related to Merge node fails to output data on false branch during test step · Issue #13593 · n8n-io/n8n · GitHub ?

8

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