Indefinite wait in n8n
Why Wait nodes without timeout can hang your workflow forever
What is this issue?
An indefinite wait occurs when a Wait node is configured to wait for an external event (like a webhook callback) but has no timeout configured. If the expected event never arrives, the workflow will wait forever.
Common scenarios:
•Wait node waiting for webhook that never fires•Resume URL shared but never accessed•External system fails to send callback•Wait for form submission that is abandoned
Why is this dangerous?
Resource lock
Each waiting execution holds memory and a slot, limiting concurrent workflows.
Silent failures
The workflow appears 'running' but is actually stuck, masking the real issue.
Orphaned executions
These executions accumulate over time, cluttering your execution history.
Business process stalls
Workflows representing business processes remain incomplete indefinitely.
How to fix it
- 1
Set Wait timeout
Configure a maximum wait time in the Wait node settings (e.g., 24 hours, 7 days).
- 2
Add timeout branch
Handle the timeout case with an alternate flow to notify users or retry.
- 3
Use workflow timeout
Set a global timeout in workflow settings as a safety net.
- 4
Monitor waiting executions
Set up alerts for executions stuck in waiting state beyond expected time.
Scan your workflow now
Upload your n8n workflow JSON and detect Wait nodes without proper timeout configuration.