I’ve observed an unexpected behavior with the Merge node in n8n when it has more than two input connections. When connecting three or more upstream nodes to the Merge node, if one of the inputs takes significantly longer to produce output (e.g., due to a delay or long-running operation), the Merge node sometimes does not wait for this input to be ready before proceeding, leading to incomplete or incorrect merge operations.
When using only two inputs, the Merge node appears to function as expected, correctly waiting for both inputs to be ready before executing its merge logic. The issue seems to manifest specifically when the number of inputs is greater than 2.
n8n Version: 1.88.0
platform: macos 15.4