Timeout not configured in n8n
Why workflows without timeouts can hang indefinitely and consume server resources
What is this issue?
Without an execution timeout, a workflow can run indefinitely if it gets stuck waiting for an external service, enters an infinite loop, or encounters a deadlock. These 'zombie' executions consume memory and CPU.
Scenarios that cause hanging:
•External API that never responds•Database query taking hours due to missing index•Wait node without timeout waiting for webhook that never comes•Infinite loop in Code node
Why is this dangerous?
Resource exhaustion
Each stuck execution consumes memory and a worker slot, eventually preventing new workflows from running.
Hidden failures
The execution appears 'running' forever but is actually stuck, masking the underlying issue.
Cost accumulation
Zombie processes increase cloud hosting costs as resources remain allocated.
Queue blocking
If using concurrency limits, stuck executions block the queue for healthy workflows.
How to fix it
- 1
Set workflow timeout
Go to workflow Settings and set a 'Timeout' value appropriate for your workflow (e.g., 300 seconds for most workflows).
- 2
Configure global timeout
Set EXECUTIONS_TIMEOUT environment variable to enforce a maximum execution time across all workflows.
- 3
Add node-level timeouts
For HTTP requests, configure specific timeout values in the node options.
- 4
Implement health monitoring
Set up alerts for executions running longer than expected to catch issues early.
Scan your workflow now
Upload your n8n workflow JSON and detect workflows missing timeout configuration.