We have 2 Workflows, the 1º should take no more than 10 seconds (10000ms) to complete.
The second one, should not take more than 30 seconds (30000ms).
The problem is because the 2º one is called by the first, and its assumes the 1º Timeout configuration, and its been cancelled after 10 seconds.
How to avoid that ?
n8n
2
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:
In workflow settings you can edit the timeout duration. Is this what you are looking for?


No, i’m saying that this timeout is not respected if the previous workflow has a minor timeout setting.
Wait For Sub-Workflow Completion
if this property was setted false, it should ignore the previous workflow timeout.
And its not.
system
Closed
6
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.