Code runner issue

[DueIQ_Mgmt]

I need help fixing a persistent code runner issue that is happening in all my workspaces that have a code node. This is something that suddenly started ocurring two days ago. I have been using these workspaces perfectly fine for several months.

Describe the problem/error/question

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.

What is the error message (if any)?

Please share your workflow

{
  "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.22 (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)"
    ]
  }
}

Share the output returned by the last 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”: “1.123.22 (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:605:17)“,
" at processTimers (node:internal/timers:541: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:

[Anshul_Namdev]

Hi @DueIQ_Mgmt Welcome!
First i would consider telling you that you should restart your current workspace so that if there is something wrong it would be fixed as this issue is known and mostly gets fixed with a reboot, and if this did not helped consider updating to the latest stable cloud version. Let me know if that helps.

[houda_ben]

Hi @DueIQ_Mgmt

Look at this thread, they already have some answers for your issue, if nothing happens, I suggest emailing [email protected]

Task runner timeout on n8n Cloud - Code nodes failing for a week

+1, I’m seeing the same on self-hosted as well, but only in one specific workflow. Most of my other workflows run fine. I already tried increasing N8N_RUNNERS_TASK_TIMEOUT, but that didn’t change anything. What did help was reducing the amount of input data passed into the Code node by batching (using the Loop/Batching approach). In my case: 1000 rows at once fails basically every time ~500 rows sometimes fails ~100 rows has been stable so far I also checked the logs, but there’s n…

[DueIQ_Mgmt]

Thanks for the recommendation. The strange thing is that this workspace has been working perfectly fine for about 1 month and suddenly now it is having the code runner issue in all of the code nodes. And I am not even sending 50 rows. Super frustrating. If this continue I will have to completely get out of n8n and convert all the coding to python. With AI, doing this is not such a big burden as it was in the past.

[houda_ben]

Totally understand, this is a real infrastructure issue on n8n’s side and you shouldn’t be dealing with it. Reach out to [email protected] with your instance URL and ask them to restart your task runner. Other users with the exact same issue got it resolved quickly once the n8n team looked at it directly.

[DueIQ_Mgmt]

All, I just changed n8n versions to a stable one in the past and everything is working fine now.

[DueIQ_Mgmt]

The issue was the n8n version. The latest one does not work.