Help with Wait Node: Flows Stuck in “Waiting” Status After Time Passed
Describe the problem/error/question:
Hello amazing n8n community,
I’ve been working on a complex workflow where I’m using multiple Wait nodes to manage timed actions and delays. However, I’m encountering an issue where certain executions seem to get stuck in a “waiting” status even after the configured time has passed.
I’ve tried different configurations, such as tweaking the “Execute Once” setting and adjusting my time intervals, but the problem persists. The flow just doesn’t resume when it should. I’m unsure whether this is due to a misconfiguration on my end or if there’s an underlying bug.
Has anyone experienced this issue before? Are there any best practices that you would recommend for dealing with Wait nodes in larger workflows? Any help would be appreciated!
No specific error message, the execution remains stuck in “waiting” indefinitely.
What I’m hoping to achieve:
I’d love to understand:
If there are any best practices to avoid issues with Wait nodes.
If others have encountered similar bugs, and how they fixed them.
If this is a known issue that requires a patch or update from the n8n team.
Thank you all in advance for your insights and help! I appreciate this community’s support and knowledge-sharing, and I’m looking forward to any advice you can offer.
Does the workflow get stuck always on the same waiting node or does it vary which one lags?
Do these eventually pick back up and continue the execution?
At the moment, the workflow always gets stuck at the same Wait node, regardless of other factors. The time is set using an “expression”, and even though the specified time has already passed, the workflow doesn’t resume execution—it remains indefinitely in the “waiting” status.
Additionally, I’ve reviewed some records where you can clearly see that the configured time has elapsed in the same timezone as the workflow, but it still fails to continue. I’m happy to provide those records if needed. Any guidance or suggestions would be greatly appreciated. Thanks again!
Since you’re using an expression that targets one of your code nodes, is the output of the Calendly Data Cleanup node expected?
Also, since you’re using n8n on cloud, if you want, send me your username in a PM and we can look into the instance logs to try and get a clearer picture of what is stalling that node.
Same issue , stuck always but not in the same node , sometimes on the loop node and some times on the if node and other times at http request node … sadly
