n8n - 💡(How to fix) Fix Merge behavior inconsistent/unmanageable

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
RAW_BUFFERClick to expand / collapse

Bug Description

A Merge(append) node will or won't pass data depending inexplicably on the overall workflow structure. The execution finishes at the node prematurely under certain conditions, with no apparent relation to the data being passed into it and no errors indicated.

<img width="1387" height="256" alt="Image" src="https://github.com/user-attachments/assets/77879977-d365-4cd3-83f1-1967fe757d7d" /> <img width="1387" height="256" alt="Image" src="https://github.com/user-attachments/assets/07ee8346-2c8e-4bf1-9256-918a29476b1f" />

To Reproduce

See attached MRE. Making or breaking the connection between NOP and Wait changes node behavior.

test2.json

Expected behavior

The node functions both predictably and consistently in a way that allows it to be applied in practice.

Debug Info

Operating System

Windows 22H2

n8n Version

2.20.7-exp.0

Node.js Version

24.14.1

Database

SQLite (default)

Execution mode

main (default)

Hosting

self hosted

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

FAQ

Expected behavior

The node functions both predictably and consistently in a way that allows it to be applied in practice.

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING