“I am on n8n Cloud and all my Code nodes time out after 60 seconds with ‘Task request timed out after 60 seconds — task runner is down, not ready, or at capacity.’ My instance is rescriptgenetics.app.n8n.cloud. This is a known TaskRunner issue — please disable TaskRunners on my instance.”
Since this is n8n Cloud and all Code nodes are timing out at 60 seconds, this feels more like something n8n support needs to investigate on the instance/task-runner side. Community users wouldn’t be able to disable TaskRunners for a cloud instance directly anyway.
I’d send support the instance URL, a failed execution ID, timestamp, and the exact error:
Task request timed out after 60 seconds — task runner is down, not ready, or at capacity
One useful test is to create a brand-new workflow with a single Code node that only does something simple like:
return [{ json: { ok: true } }];
If even that times out, that’s pretty strong evidence the issue isn’t your workflow logic and is more likely related to the instance/task-runner environment itself.
Hi @Aura_Gene
Your Code nodes are failing because a new n8n Cloud feature called “TaskRunners” is glitching on your instance, causing it to freeze and time out after 60 seconds regardless of how simple your code is. This is a known system-level issue that cannot be fixed from within your workflow settings. To resolve this, you need to email help@n8n.io and ask them to manually disable TaskRunners for your instance (rescriptgenetics.app.n8n.cloud), which will return your Code nodes to the stable, original way of running.
@Aura_Gene if urgency is high, noting that self-hosted n8n lets you control TaskRunner config directly via N8N_RUNNERS_ENABLED=false