# Timeout Error in multiple nodes, across multiple workflows **URL:** \ **Category:** Questions\ **Created:** [June 9, 2022, 4:42am UTC](https://community.n8n.io/t/timeout-error-in-multiple-nodes-across-multiple-workflows/14716 "2022-06-09T04:42:50Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![shrey-42](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/shrey-42/32/3437_2.png) [@shrey-42](https://community.n8n.io/u/shrey-42)\ **Post date:** [June 9, 2022, 4:42am UTC](https://community.n8n.io/t/timeout-error-in-multiple-nodes-across-multiple-workflows/14716/1 "2022-06-09T04:42:50Z")
## Describe the issue/error/question I’m seeing multiple workflows fail due to nodes failing with Timeout error. The nodes failing so far: Telegram, Airtable, Discord Error: ```auto {"message":"timeout of 300000ms exceeded","name":"Error","stack":"Error: timeout of 300000ms exceeded\n at createError (/usr/local/lib/node_modules/n8n/node_modules/axios/lib/core/createError.js:16:15)\n at RedirectableRequest.handleRequestTimeout (/usr/local/lib/node_modules/n8n/node_modules/axios/lib/adapters/http.js:303:16)\n at RedirectableRequest.emit (node:events:527:28)\n at RedirectableRequest.emit (node:domain:475:12)\n at Timeout. (/usr/local/lib/node_modules/n8n/node_modules/follow-redirects/index.js:164:12)\n at listOnTimeout (node:internal/timers:559:17)\n at processTimers (node:internal/timers:502:7)","code":"ECONNABORTED"} ``` The workflows have default timeout of at least an hour. Also, this is the first time that i’ve seen this error. ## Information on your n8n setup - **n8n version:** 0.179.0 - **Database you’re using (default: SQLite):** Postgres - **Running n8n with the execution process [own(default), main]:** main - **Running n8n via [Docker, npm, n8n.cloud, desktop app]:** Docker ---
**Author:** ![MutedJam](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/mutedjam/32/70851_2.png) [@MutedJam](https://community.n8n.io/u/MutedJam)\ **Post date:** [June 9, 2022, 7:04am UTC](https://community.n8n.io/t/timeout-error-in-multiple-nodes-across-multiple-workflows/14716/2 "2022-06-09T07:04:55Z")
Hey @shrey-42, this sounds like either your system or your network (or possibly your database) isn’t quite working as expected or doesn’t have enough resources. Could you try running your failed workflow in a different environment and verify whether the errors still persist there? You can spin up n8n using docker and a local SQLite database by running `docker run it --rm --name n8n -p 5678:5678 -v ~/.n8n:/home/node/.n8n n8nio/n8n:0.179.0`. This would also be a great cross-check for the other error you have [reported here](http://community.n8n.io/t/trigger-related-silent-bug-after-update-to-0-180-0/14692). It’s also worth mentioning that running n8n in [main](https://docs.n8n.io/hosting/scaling/execution-modes-processes/#main) mode means that all workflows are executed in the main n8n process. So if one of your executions is particularly demanding it could possibly block other executions. You could verify if this mode might be the bottleneck here by (temporarily) switching to `own` mode. ---
**Author:** ![shrey-42](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/shrey-42/32/3437_2.png) [@shrey-42](https://community.n8n.io/u/shrey-42)\ **Post date:** [June 9, 2022, 7:16am UTC](https://community.n8n.io/t/timeout-error-in-multiple-nodes-across-multiple-workflows/14716/3 "2022-06-09T07:16:20Z")
Hi @MutedJam , i actually came across this issue in Github, already. > > > \*\*Describe the bug\*\* > Hello, seems, the lambda node in n8n has a built-in timeou…t set to 5 min despite the settings of the lambda function in the AWS. I've configured a dummy lambda to invokes for 12 minutes. From AWS console everything is working fine, but from n8n workflow I'm getting the timeout error: > \`\`\` > { > "message": "timeout of 300000ms exceeded", > "name": "Error", > "stack": "Error: timeout of 300000ms exceeded at createError (/usr/local/lib/node\_modules/n8n/node\_modules/axios/lib/core/createError.js:16:15) at RedirectableRequest.handleRequestTimeout (/usr/local/lib/node\_modules/n8n/node\_modules/axios/lib/adapters/http.js:303:16) at RedirectableRequest.emit (node:events:527:28) at Timeout.\ (/usr/local/lib/node\_modules/n8n/node\_modules/follow-redirects/index.js:164:12) at listOnTimeout (node:internal/timers:559:17) at processTimers (node:internal/timers:502:7)", > "code": "ECONNABORTED" > } > \`\`\` > > \*\*To Reproduce\*\* > Steps to reproduce the behavior: > 1. Create a lambda function in AWS (python 3.6+): > \`\`\`py > import time > > def lambda\_handler(event, context): > time.sleep(12\*60) > return { > 'statusCode': 200, > 'body': 'waited for 12 mins' > } > > \`\`\` > 2. Push the deploy button > 3. Configure the timeout to the 15 minutes (max for lambda function) > 4. Run it via n8n workflow with empty json \`{}\` > 5. See error > > \*\*Expected behavior\*\* > After 12 of minutes the worflow will return some data > > \*\*Environment (please complete the following information):\*\* > - OS: docker > - n8n Version 0.176.0 So, even though there might be an issue in my environment (that i need to diagnose), the node timeout bug (or feature) is also an issue. As docker’s not properly my expertise, it would be a great help if you could also point out to me some resource/link on how to debug the n8n container’s interactions with the docker system. Because, i’m suddenly seeing all these issues in my instance (also multiple container restarts happening every hour), i suspect that the docker-n8n relationship is somehow disturbed. This does not seem to affect some of the other containers running in the same docker system (postgres, traefik, portainer etc.) Also, i would like to explore the **own** mode, but my understanding is that it would demand more resources from the environment and might actually hinder simultaneous, large number of executions. Do correct me if i’m wrong. Thanks. ---
**Author:** ![MutedJam](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/mutedjam/32/70851_2.png) [@MutedJam](https://community.n8n.io/u/MutedJam)\ **Post date:** [June 9, 2022, 7:24am UTC](https://community.n8n.io/t/timeout-error-in-multiple-nodes-across-multiple-workflows/14716/4 "2022-06-09T07:24:07Z")
> [@shrey-42](#): > > Also, i would like to explore the **own** mode, but my understanding is that it would demand more resources from the environment and might actually hinder simultaneous, large number of executions. Do correct me if i’m wrong. So own mode can lead to a higher overall system load (because n8n will use more than 1 CPU core), but it would also mean that a single and very demanding execution isn’t blocking everything else happening in n8n. If the switch to own mode doesn’t improve the situation, my first step with debugging your docker environment would be what I have suggested already. Isolate the problematic workflow and run it in a different environment to verify whether this is indeed a problem with your specific environment or with the workflow in general.