n8n - 💡(How to fix) Fix All Code nodes failing in n8n Cloud (v1.123.27) — Task runner not picking tasks (timeout after 60s) [1 comments, 2 participants]

Describe the problem/error/question

All workflows that include a Code node are failing in n8n Cloud (v1.123.27). This issue is not tied to a specific workflow. It affects multiple workflows across my workspace, including production ones. The error suggests that the Code node task is not being picked up by a task runner within the timeout window. Given that even simple workflows fail, this appears to be a task runner availability/capacity issue rather than a problem with workflow logic. This is currently impacting production workflows.

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. 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.

Stack trace:

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.<anonymous> (/usr/local/lib/node_modules/n8n/src/task-runners/task-broker/task-broker.service.ts:102:9) at listOnTimeout (node:internal/timers:605:17) at processTimers (node:internal/timers:541:7)

⸻

Please share your workflow/screenshots/recording

This happens across multiple workflows. Below is a minimal reproduction:

Minimal failing workflow

• Manual Trigger
• Code node with:

return [{ json: { ok: true } }];

This minimal setup also fails with the same error, which suggests the issue is not related to workflow complexity.

⸻

Share the output returned by the last node

The failing node is the Code node. It does not return normal output and instead returns:

{ "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.<br/><br/>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": "1.123.27 (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.<anonymous> (/usr/local/lib/node_modules/n8n/src/task-runners/task-broker/task-broker.service.ts:102:9)", " at listOnTimeout (node:internal/timers:605:17)", " at processTimers (node:internal/timers:541:7)" ] } }

⸻

Debug info

core

• n8nVersion: 1.123.27
• platform: docker (cloud)
• nodeJsVersion: 24.13.1
• nodeEnv: production
• database: sqlite
• executionMode: regular
• concurrency: 50
• license: enterprise (sandbox)

storage

• success: all
• error: all
• progress: false
• manual: true
• binaryMode: filesystem

pruning

• enabled: true
• maxAge: 720 hours
• maxCount: 25000 executions

client

• userAgent: mozilla/5.0 (macintosh; intel mac os x 10_15_7) applewebkit/537.36 (khtml, like gecko) chrome/147.0.0.0 safari/537.36
• isTouchDevice: false

Generated at: 2026-04-22T09:59:09.644Z

Additional notes

• This affects all workflows containing Code nodes, not just one specific workflow.
• Workflows without Code nodes appear to work normally.
• The issue started suddenly and was not caused by changes in the workflows.
• This looks like a task runner availability or capacity issue for this workspace. Please check the health and availability of task runners for this instance.