Issue: Unexpected Behavior When Using merge
Node
Description
I’m experiencing unexpected behavior when using the merge
node in my workflow. Here’s what’s happening:
- When I add the
merge
node, the workflow breaks.
-
When I remove the
merge
node, everything runs perfectly.
-
I use the
merge
node in other workflows without any issues, so this seems to be a specific case.
Context
To avoid generating a response for every message sent, I integrated Redis as a way to control flow or rate limit responses.
In this setup, I need to merge inputs before proceeding, which is why including the merge
node is essential.
What I Need
Any suggestions or guidance on how to:
- Use the
merge
node properly in this scenario. - Diagnose why it’s breaking the workflow in this specific case.
What is the error message (if any)?
Workflow execution had an error
Cannot read properties of undefined (reading ‘execute’)
Please share your workflow
(Select the nodes on your canvas and use the keyboard shortcuts CMD+C/CTRL+C and CMD+V/CTRL+V to copy and paste the workflow.)
Share the output returned by the last node
Information on your n8n setup
- n8n version: Version 1.90.2
- Database (default: SQLite):
- n8n EXECUTIONS_PROCESS setting (default: own, main):
- Running n8n via (Docker, npm, n8n cloud, desktop app): Railway template
- Operating system: