Code node task was not matched to a runner

Questions
1

I’m getting this error on every execution of a Code node, even with very small item counts (5–20 items):

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:305:17)
at LocalTaskRequester.onMessage (/usr/local/lib/node_modules/n8n/src/task-runners/task-managers/task-requester.ts:273:10)
at TaskBroker.handleRequestTimeout (/usr/local/lib/node_modules/n8n/src/task-runners/task-broker/task-broker.service.ts:124:50)
at Timeout. (/usr/local/lib/node_modules/n8n/src/task-runners/task-broker/task-broker.service.ts:110:9)
at listOnTimeout (node:internal/timers:605:17)
at processTimers (node:internal/timers:541:7)

What I’ve already ruled out:

  • Not a data volume issue — fails consistently even with just 5 items via a Limit node before the Code node
  • Not an inefficient code issue — the code is simple object mapping + one regex on a short string, no loops, no external calls (code below)
  • Not a malformed JSON issue — the data has already passed through several standard nodes (Split Out, Filter, IF) without any errors before reaching the Code node
2

Hi @Philip_Hoerschelmann Welcome!
are you on n8n Cloud or self hosted? If Cloud, “not matched to a runner” is a platform side runner issue that you can’t fix from your end, and the move is to reach out to support. If self hosted, share how you run n8n (Docker, npm, single container vs queue mode) and whether you have task runners set up in external mode, and we can debug the runner connection from there.