I’m using n8n Cloud and my workflow fails when it reaches a Code node.
The execution times out after ~60 seconds with a “task runner not matched” error.
It looks like the Code node task is not being picked up by a task runner (runner down / not ready / at capacity).
I want to know what can cause this on n8n Cloud and how to fix/avoid it.
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.
error message : 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.
n8n version
1.123.5 (Cloud)
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. (/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)
output :
No output – execution fails before producing any data from the Code node.
This error happens before your code executes. It usually means the system cannot transfer the data to the Task Runner in time, either because the runners are down or the data payload is too large.
Please perform this quick test: Create a new, empty workflow with only one Code node running this simple script: return { json: { test: "ok" } };
Scenario A: The test FAILS
Cause: Your Cloud instance’s task runners are down or unresponsive.
Action: You must contact n8n support to restart/fix your instance.
Scenario B: The test WORKS
Cause: The input data in your original workflow is too heavy (e.g., thousands of items or large Binary files). The system times out trying to send this data to the runner.
Action: Place an Edit Fields node before the Code node. Configure it to remove binary data and keep only the specific JSON fields your script needs.
If you’ve already confirmed this happens even in a brand-new workflow with a minimal Code node, the next step is to escalate with your workspace details.
When you contact them / post for escalation, include:
your Cloud workspace URL
your n8n version
a couple of failing execution IDs + timestamps
“Help → About n8n → Copy debug information” (paste it)
Just to clarify, this error is happening BEFORE your code even runs. So the problem isn’t with your JavaScript itself, it’s with the payload arriving at the Code node.
That means anything you do to reduce the size, volume, or complexity of the data before it hits the Code node should help.
Here’s something you can try right away without waiting for support:
Add an Edit Fields (Set) node right before the Code node and keep only the minimal JSON fields you actually need — strip out any binary data or large objects. Also make sure you’re not sending a huge number of items at once. Using Split in Batches to process data in smaller chunks often helps avoid these timeouts.
And if your Code node is only doing simple mapping or filtering, consider replacing it with native nodes like IF, Set, or Item Lists. That way you avoid the task runner entirely and the timeout won’t even be a factor.
Hi there, I am experiencing the same issue here. No response from support, aside from one AI generated reply. Did anybody find a workaround / fix I can try?
Just to clarify: even the basic, “off the shelf” JS code node times out, so it is not an issue of the code itself or the amount of inputs it is processing. Additionally, I’ve tested JS code nodes in another cloud acct I have and those run perfectly fine.