I have problem with merge node behaviour where in real it does not wait both inputs

Questions
1

Describe the problem/error/question

I have a merge node with condition where it has to wait for 2 inputs and then always output just the input 2 . Where as in real , It just overwrites the later received input as output. I sense the problem is with wait node receiving 3 items , which makes it run 3 times . Please suggest how to overcome this error , I always need output from set node and then wait node only then it has to proceed further with just set node output ONLY.
@Jon , @MutedJam hoping some one can help.

What is the error message (if any)?

Merge node behaviour is not as expected.

Please share your workflow

never mind I resolved it by using multiple merge nodes , the wait node caused a problem

(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:
  • Database (default: SQLite):
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app):
  • Operating system:
2

It looks like your topic is missing some important information. Could you provide the following if applicable.

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

Hey @Siya,

Do you have an example workflow you can share that showed the issue you were seeing… that is if you want us to still look into it.

4

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