# Strange behavior of merge node **URL:** \ **Category:** Questions\ **Tags:** node, merge\ **Created:** [August 19, 2025, 2:17pm UTC](https://community.n8n.io/t/strange-behavior-of-merge-node/171783 "2025-08-19T14:17:27Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![aemkey](https://avatars.discourse-cdn.com/v4/letter/a/f17d59/32.png) [@aemkey](https://community.n8n.io/u/aemkey)\ **Post date:** [August 19, 2025, 2:17pm UTC](https://community.n8n.io/t/strange-behavior-of-merge-node/171783/1 "2025-08-19T14:17:27Z")
## 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](https://europe1.discourse-cdn.com/n8n/original/3X/7/5/75c3ff499bc7ad95cae399039a4d0d72a8b2f5c9.png) Filter set to fourth run ![grafik](https://europe1.discourse-cdn.com/n8n/original/3X/e/9/e98183ab960fe06fc703c9284e6b5fca7f3051a4.png) ## 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** ---
**Author:** ![swoonunits](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/swoonunits/32/108170_2.png) [@swoonunits](https://community.n8n.io/u/swoonunits)\ **Post date:** [August 19, 2025, 3:13pm UTC](https://community.n8n.io/t/strange-behavior-of-merge-node/171783/2 "2025-08-19T15:13:59Z")
could you please elaborate what you are trying to achieve with the workflow? ---
**Author:** ![aemkey](https://avatars.discourse-cdn.com/v4/letter/a/f17d59/32.png) [@aemkey](https://community.n8n.io/u/aemkey)\ **Post date:** [August 19, 2025, 5:44pm UTC](https://community.n8n.io/t/strange-behavior-of-merge-node/171783/3 "2025-08-19T17:44:19Z")
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. ---
**Author:** ![aemkey](https://avatars.discourse-cdn.com/v4/letter/a/f17d59/32.png) [@aemkey](https://community.n8n.io/u/aemkey)\ **Post date:** [August 22, 2025, 12:00pm UTC](https://community.n8n.io/t/strange-behavior-of-merge-node/171783/4 "2025-08-22T12:00:10Z")
Does anyone know if this is a bug? ---
**Author:** ![aemkey](https://avatars.discourse-cdn.com/v4/letter/a/f17d59/32.png) [@aemkey](https://community.n8n.io/u/aemkey)\ **Post date:** [September 1, 2025, 7:11am UTC](https://community.n8n.io/t/strange-behavior-of-merge-node/171783/5 "2025-09-01T07:11:12Z")
Not solved yet ---
**Author:** ![aemkey](https://avatars.discourse-cdn.com/v4/letter/a/f17d59/32.png) [@aemkey](https://community.n8n.io/u/aemkey)\ **Post date:** [September 9, 2025, 6:40am UTC](https://community.n8n.io/t/strange-behavior-of-merge-node/171783/7 "2025-09-09T06:40:26Z")
Is this somehow related to [Merge node fails to output data on false branch during test step · Issue #13593 · n8n-io/n8n · GitHub](https://github.com/n8n-io/n8n/issues/13593) ? ---
**Author:** ![system](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/system/32/195824_2.png) [@system](https://community.n8n.io/u/system)\ **Post date:** [December 8, 2025, 6:40am UTC](https://community.n8n.io/t/strange-behavior-of-merge-node/171783/8 "2025-12-08T06:40:33Z")
Closed on December 8, 2025, 6:40am UTC This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.