This isn’t really a bug in the workflow but more of an execution limit that is being hit particularly because you are on n8n Cloud. There is a 60 second hard execution timeout per node that is determined by the task runner. This can start being reached by nodes that do heavier processing or rely on slower APIs.
Some things that can help:
-Split up longer running logic in to smaller executions, so break the workflow up but persist the state
-If you need to wait for an external API or something to process it is best to use a Webhook that way your workflow isn’t stuck running and waiting but only starts/continues when data is actually ready.
-Try to trim and filter data before putting large payloads into Code nodes
-Finally consider self-hosting if you can this will allow for longer execution times and control over timeouts
If this just started happening it could be something external, you may want to open up a support ticket on the cloud for further examination.
For issues specifically related to task runners, you’ll need to open a support ticket with the n8n team directly, they’re the ones who can properly investigate and address the root cause.
These won’t resolve the underlying cause, but they can reduce the frequency of the issue:
Break large Code nodes into several smaller ones
Replace Code nodes with native nodes (Set, IF, Item Lists, Merge) whenever possible
Reduce concurrency (use Split in Batches, fewer parallel executions)
Avoid heavy processing immediately after synchronous Webhooks
Hope the workarounds help in the meantime! Let me know if you need anything else. Get help
I am facing a timeout issue with the Python node on n8n Cloud.
Details:
n8n version: 2.6.3 (Cloud)
Issue: Python node fails with timeout even when using a very simple one-line code like return True or 1 + 1
JavaScript Code node works fine with the same workflow
This issue also happens in a brand-new workflow with only a Manual Trigger and Python node
I have already tried updating the version and clearing all executions, but the issue still persists
Error message:
Task request timed out after 60 seconds
Stack trace:
Error: Task request timed out after 60 seconds
at LocalTaskRequester.requestExpired
at LocalTaskRequester.onMessage
at TaskBroker.handleRequestTimeout
It looks like the Python task runner is not responding properly for my workspace.
Could you please check ?
Your Code node task was not matched to a runner within the timeout period. This indicates that the task runner is currently down, or not ready, or at capacity, so it cannot service your task.
If you are repeatedly executing Code nodes with long-running tasks across your instance, please space them apart to give the runner time to catch up. If this does not describe your use case, please open a GitHub issue or reach out to support.
Are you using docker, or how are you deploying the main and runner instances? How are they connected? Right now, you are only sharing error messages which are standard and offer no new information. We need to understand your setup before we can help you.
How did you install n8n? Docker or npm?
If you used docker, are you also using docker-compose?
What does compose.yml say right now? Don’t forget to remove keys and other private info.
What is the underlying OS? Linux Windows Mac?
