Is there a recommended/Best practice method of hanlding timeouts? Currently, if a workflow timeouts, it gets cancelled. But there is no way of being alerted.
It looks like your topic is missing some important information. Could you provide the following if applicable.
- n8n version:
- Database (default: SQLite):
- n8n EXECUTIONS_PROCESS setting (default: own, main):
- Running n8n via (Docker, npm, n8n cloud, desktop app):
- Operating system:
Hi @jtoh
You can use an error workflow for that matter as any timed-out workflow will change the execution status from cancelled to eventually Error.
Here’s a simple template to get you started:
You can read more about Error Handling in n8n here:
1 Like
How long does it take for execution status to change from Cancelled to Error? In my instance, it shows that it took over 2 days. Is this expected behavior? And are there any plans to shorten this wait time?
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.