I am encountering two critical issues with our n8n setup:
Upon activating a workflow, a single trigger results in multiple (typically four) executions—only one succeeds while the others fail. How is this happening? I do not understand how a single request can at the same time pass and fail IF node. Is there something i am missing?
Hi there!
Could you please tell me more about your node? I faced a similar situation last week with a WhatsApp workflow. My solution was to ensure the filtration for ‘fromMe’ messages. Sometimes, the workflow was reading my own messages as input, which was the root of my problem. This might be a clue in your case.
Hey @Mladen_Savic , I Think you can use the Switch node to separate the workflows in this case. If that doesn’t work, try updating your n8n version — I faced similar issues before, but updating to a newer version helped me resolve them.
Hi Julian, thnx for reaching out and taking interest in my issue. I am using WhatsApp trigger node as workflow input and WhatsApp message node as output node. Basically what happens is that the trigger node schema for failed executions is different. As a consequence, the last node which uses {{ $(‘WhatsApp Trigger’).item.json.contacts[0].wa_id }} fails to return a message. That in itself is not a problem, bc even if it did manage to send back a message, it would make no sense to receive 4 answers instead of 1 when sending a request. Hope i am making sense 
Hi Sal, thank you for taking interest in this issue. What do you mean by separating the workflows? I’m still new at this 
However i did try switching to new version but to no avail.
Hi @Sai_Durga_Yaswanth , May I know in which version you faced this issue? Bcz I’m currently facing this multiple executions issue while using 1.91.3 so just to make sure that I need upgrade or not.
Hi @Mladen_Savic , Did you got any resolution for this issue? I’m facing this issue when I get the responses from open web ui and after the response got triggered in n8n then the multiple executions are happening. So it’ll be very helpful if I get any clue to resolve this issue from your process.
Hey @Kranthi-vadapalli, sorry for the late reply. What I actually found out is that the issue could be attributed to WhatsApp sending follow up messages (3 validation messages for every single message i send) which as it turns out is quite common when using WhastApp cloud. The errors were popping up as i did not have a node/parser that would handle data output from these follow up messages. Hope this helps.
Thanks @Mladen_Savic. I think this would be a bit related to my case as well. I need to check the output responses from open webui which sends duplicate responses to n8n. This might triggering the executions multiple times. Thanks for giving a insight
@Mladen_Savic .
1 Like
Just wanted to follow up on this topic and share some info in case you still need it. To disable the follow up messages go to your WhatsApp node, double-click it, Click add option and you should see the “Receive Message Status Updates” drop down. By default the item “All” is probably already active. Uncheck it and the “Receive Message Status Updates” drop down should now be completely empty. If your Workflow is in active mode, make sure you save it. That should do it.