N8n Workflow Executes Multiple Times After Wait Node

Questions
,
1

Describe the problem/error/question

I’ve created an n8n workflow which integrates Retell AI with my company’s GoHighLevel CRM. My n8n workflow calls back new leads if Retell indicates the lead did not pick up. After a couple of calls, it uses the wait node to wait for a certain date and time before calling them back. Then it checks if the lead’s contact id is still in the google sheet I created which temporarily stores leads that are queued to be called back. However, when I look at the execution history, it seems to have executed the workflow 8 times for each call attempt after the wait node finished running. I cleared the google sheets, so for each workflow it looked up the row with the contact id, but didn’t find it, so it didn’t output anything and the workflow stopped as a result. However, it seems to have run 7 other times, each within a second after its previous execution. We also had a lead say that they were called 8 times in a row at once. Why would this be happening, and how do I prevent it from happening?

What is the error message (if any)?

There is no error message. The workflow executes successfully every time, but it just executes more times than I had intended.

Please share your workflow

I could not paste the node because it told me that the number of characters in my topic well exceed the limit. So I’ve attached a photo instead.

Screenshot 2025-08-21 132724
Screenshot 2025-08-21 1327241415×408 62.5 KB

Share the output returned by the last node

Information on your n8n setup

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

Try in the last node of your workflow, use a “execute once”.
Settings → Execute Once

For nodes: Delete Rows Or Columns on the seets.
Create Call Back
Delete Rows Or Columns on the seets1.

1 Like
4

This worked, thanks!

1 Like
5

Can you mark my answer with “solution”?

6

Hi, I’m not sure if Execute Once will work in my case. I have some looping/retrying logic in my workflow, and I expect a node to be called many times until it reaches a specific condition. I’m just wondering if this is an N8n issue that should be fixed rather than using the Execute Once as a workaround?

1 Like
7

This seems related to this issue here as well,

The linked fix is already released, but I still see the issue happening.

Also tested using the Execute Once setting in the retry looping, and it still execute the nodes, we may be able to workaround this issue.

8

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