I am encountering an issue with the Wait node in my workflow. When I set the time and date in ISO format to be in the past, the execution gets stuck indefinitely. The following is an example setup that causes the issue:
It looks like your topic is missing some important information. Could you provide the following if applicable.
I also had clients with major issues with Wait nodes. Set correctly in the future.
I saw historically that there were a few patched bugs like “bad timezones” that can cause this. I think one was in 1.20.1
We had regular Wait’s run indefinitely. Were on 1.36.1, updated to 1.39.1. No longer did NEW Wait issue occur, except old Wait runs were permanently stuck in the executions queue. Not only that, they would somehow CONTINUE to proc hourly. SPAMMING my clients leads with emails. Still executing from well over a week ago. Oh, and the scenarios were all off by this point 24hr+.
The Waits were set to 1hr and 1.5hr. See how it says “waiting in 12000 minutes”:
I’ve been trying for many days now to communicate with support to look into the issue in the backend. I provided very detailed information. No real response.
It finally took deleting both the suspect workflows with stuck queue’s, pasting them fresh, then an n8n restart.
Support did not mention a solution or recommend this, I’ve been actively follow up with more details, ghosted. My client is a paying customer with multiple cloud instances.
They may need to recommend this for future issues of similar caliber.
I’d just appreciate if support can log and look into this.
Well… all I can advice - do not use wait node as a cron node 
What is the use case to use the wait node in that way?
I’m developing a workflow that triggers specific actions based on predetermined times and dates. This workflow is integrated with Notion, enabling automated tasks to be executed precisely at the scheduled times and dates.
Would the Wait node not be recommended for this use case?
I first encountered this issue in a workflow of mine that loops. When the workflow initiates a second execution, the designated time in the wait node has already passed, causing the execution to get stuck rather than continue as expected.
In older versions of n8n this wasn’t a problem
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
