Notifications
Clear all
Topic starter
Hi, I'm currently using callin.io for making calls within n8n, and I'm frequently encountering an issue where n8n workflows are automatically cancelled if a call exceeds 2 minutes.
I'm a bit stuck and would appreciate any help!
Information on your callin.io setup
- n8n version: 1.95.3
- Database (default: SQLite): N8N cloud
- n8n EXECUTIONS_PROCESS setting (default: own, main):
- Running n8n via (Docker, npm, n8n cloud, desktop app): n8n cloud
- Operating system:
Posted : 14/06/2025 4:36 am
It might be due to the Starter plan's maximum execution time.
However, it should currently be 5 minutes. Does your workflow have another timeout setting configured?
Posted : 14/06/2025 4:54 am
Topic starter
(post deleted by author)
Posted : 14/06/2025 5:05 am
Topic starter
I've also adjusted it to 5, but I suspect you're correct; it's likely due to the time limit.
Are there any potential workarounds we could explore?
Posted : 14/06/2025 5:09 am
Topic starter
Just to confirm, I'd like to know the precise duration of the entire workflow. Since this sub-workflow takes approximately 3 minutes, where are the remaining 2 minutes being utilized?
Posted : 14/06/2025 5:15 am
Ah, it's a sub-workflow.
So, what's the execution time for the main workflow?
Posted : 14/06/2025 5:45 am
Topic starter
The main workflow's total execution time is 3 minutes and 18 seconds.
Does this total time also encompass the duration of any sub-workflows?
Posted : 14/06/2025 5:58 am
Yeah, it should. So if it didn’t over 5 minutes.
You might need to email to help@callin.io and ask them what’s going on?
Posted : 14/06/2025 5:59 am
Topic starter
I'll get back to you shortly.
Posted : 14/06/2025 6:09 am