[URGENT - Cloud] Code nodes timeout "task runner not matched" - blocking production workflow

Questions
1

Describe the problem

Our production workflow “ZARO · Objetivo Semanal” has been failing for
3+ hours with:

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

This happens on EVERY Code node in this workflow, INCLUDING trivial ones
like return [{ json: { ok: true } }];.

Key findings (already investigated):

  1. Same workflow JSON was working perfectly on Aug 17, 2025. Compared
    exports byte-by-byte: code and connections are IDENTICAL (only versionId
    and 2 node X/Y positions differ).
  2. Other workflows in same workspace run fine. “My workflow 5” executes
    in 31ms, 279 runs today, 0 errors.
  3. Duplicating the problematic workflow does NOT solve it - duplicate
    also fails with same timeout.
  4. 7+ consecutive failures today, all with EXACTLY ~60s runtime - pure
    timeout, no actual execution happens.
  5. No concurrent executions running when triggering.
  6. https://status.n8n.io reports all systems operational.
  7. Insights shows this workflow avg runtime is 65.36s - right at the 60s
    timeout threshold.

Workflow

Cannot paste here (sensitive business data + 65 nodes). Available on request.

Last node output

Error JSON:

{
“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.”,
“n8nDetails”: {
“n8nVersion”: “2.20.7 (Cloud)”,
“binaryDataMode”: “filesystem”
}
}

Information on your n8n setup

  • n8n version: 2.20.7
  • Database: managed by n8n cloud
  • n8n EXECUTIONS_PROCESS setting: managed by n8n cloud
  • Running n8n via: n8n Cloud
  • Operating system: n/a (cloud)
  • Workspace URL: n8n.io - Workflow Automation
  • Last successful execution: Aug 17, 2025
  • Workflow name: ZARO · Objetivo Semanal 090526 TEST

Questions

  1. Is the Code node timeout configurable above 60s in our plan?
  2. Is there a stuck runner slot for this specific workflow that needs
    manual reset?
  3. Why does duplicating the workflow not assign a fresh runner?

This is blocking production operations. Any guidance appreciated.

Thanks,
Sergio

2

Hi @Sergio_Zaera, Welcome!
This is an infrastructural problem which requires deep inspection of your n8n instance in the cloud. For now I would recommend giving your instance a restart from the admin dashboard. If that doesn’t fix the issue, consider reaching out to these: Where To Ask N8n Questions And Get Fast Answers | Qixazow

To answer your questions:

You can configure that as an env variable, but it is not an available option on N8N Cloud instances.

because runner timeout is an instance-level problem, not a workflow-specific one, it ideally means that the runner is either busy or exhausted.