N8n Cloud 2.0.3 – Code nodes intermittently fail with “Task request timed out after 60 seconds”

Code nodes intermittently time out with “Task request timed out after 60 seconds” on n8n Cloud, even for small synchronous scripts.

Describe the problem/error/question:

I’m experiencing intermittent failures where Code nodes fail with “Task request timed out after 60 seconds” in n8n Cloud.

This started recently and affects simple, synchronous JavaScript code that previously ran instantly. The error occurs even when the code does not make network requests or heavy computations.

Additionally, when opening the workflow editor, I often see a temporary “connection lost” warning, which later resolves on its own. This suggests a possible issue with runner availability or task assignment rather than workflow logic.

What is the error message (if any)?:

Task request timed out after 60 seconds
Your Code node task was not matched to a runner within the timeout period.

Error: Task request timed out after 60 seconds
at LocalTaskRequester.requestExpired
at TaskBroker.handleRequestTimeout

Please share your workflow

Share the output returned by the last node

Error output in Build Payload node:
{
“errorMessage”: “Task request timed out after 60 seconds”,
“errorDescription”: “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.”,
“errorDetails”: {},
“n8nDetails”: {
“n8nVersion”: “2.0.3 (Cloud)”,
“binaryDataMode”: “filesystem”,
“stackTrace”: [
“Error: Task request timed out after 60 seconds”,
" at LocalTaskRequester.requestExpired (/usr/local/lib/node_modules/n8n/src/task-runners/task-managers/task-requester.ts:304:17)“,
" at LocalTaskRequester.onMessage (/usr/local/lib/node_modules/n8n/src/task-runners/task-managers/task-requester.ts:272:10)”,
" at TaskBroker.handleRequestTimeout (/usr/local/lib/node_modules/n8n/src/task-runners/task-broker/task-broker.service.ts:115:50)“,
" at Timeout. (/usr/local/lib/node_modules/n8n/src/task-runners/task-broker/task-broker.service.ts:102:9)”,
" at listOnTimeout (node:internal/timers:588:17)“,
" at processTimers (node:internal/timers:523:7)”
]
}
}

Information on your n8n setup

  • n8n version:
  • Database (default: SQLite):
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app):
  • Operating system:

same here,

basically anything that takes > 60 sec will fail with:

Task execution timed out after 60 seconds

It’s so annoying fr, I’m using an external solution which I really don’t want until this gets fixed :confused:

2 Likes

Ended up updating my n8n from 2.0.3 to
2.3.6 and it resolved the issue

2 Likes

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.