I’ve been trying to figure this out for two days and nothing is working. In my automation I have a wait node configured to resume on a webhook call. The loop over batches node that comes before it is pushing one lead through the loop, it makes a api call to Vapi to make a call and then the Wait2 nod…

Thanks everyone for you responses. I finally figured it out so I’m going to leave a rather long winded answer in case anyone else is trying to figure this out in the future (or a LLM that someones using picks up on this response). High level - the problem was a mixture of what Vapi sends over durin…

The waiting maybe not coming from wait node Might come from some node you used Human in the loop send and wait for response. So the workflow is waiting for user input something to continue.

Hey @darrell_tw thank you for the response! I don’t have any nodes in this flow that require human in the loop unfortunately.

Hey @dmo1innovate ! If you are waiting for the “completed or ended” event from Vapi, i suggest to create another workflow(and set in VAPI the callBackUrl) … And once the call ends VAPI will send a to your webhook the response (actually this is the way to do it, instead sending ‘n’ requests to Vapi …

Hey @Parintele_Damaskin ! Thanks for the response. I considered having a separate webhook response workflow but the issue is that it would explode the execution count. Each client is making 150 calls a day so that would produce 150 execution of the webhook response workflow. Take that and multiply it…

Ok… I understand. Is like you are seeing “ghost” executions? Or duplicates? Or the fact that there are “waiting” (PENDING) execution s?(couse this happens when workflow has Wait node), it gets only the slot, but not counting as execution until is processed. Without more context (more images with…

Maybe this is related to the bug mentioned here? [image] Announcing n8n version 2.0 - coming soon! Announcements The issue with the subworkflow’s waiting node is fixed. Yet, when there are multiple waiting nodes, the parent only waits for the first and uses the…

I can confirm that this issue is resolved in master. fix(core): Don't resume parent workflow when the child workflow goes into waiting (#22964) committed 01:13PM - 10 Dec 25 UTC (UTC) [image] mf…

Wait node causing multiple executions?

Questions

mohamed3nan December 11, 2025, 9:33pm 7

Maybe this is related to the bug mentioned here?

Topic		Replies	Views
Do Wait nodes create new executions or resume the same execution? Questions	4	157	October 9, 2025
WAIT node resumes and runs multiple times if there are multiple worker nodes Questions wait	16	1046	September 14, 2023
Multiple Wait for Webhook Nodes Questions node , workflow-building , wait , webhook	2	654	November 27, 2023
Wait node with on webhook call not working from the first short Questions core	3	798	April 5, 2022
Multiple webook calls overlaping Questions webhook	28	6688	January 12, 2024

Wait node causing multiple executions?

Related topics