Code node task not matched to a runner - n8n Cloud

Questions
1

Halo, saya mengalami error berikut di workflow saya di n8n Cloud:

Task request timed out

Your Code node task was not matched to a runner within the timeout period (waited 66 seconds). This indicates that the task runner is currently down, or not ready, or at capacity, so it cannot service your task.

Sudah saya coba dengan kode paling sederhana sekalipun (return $input.all();) dan tetap timeout dengan pesan yang sama. Ini terjadi di semua Code node pada workflow saya, bukan hanya satu.

Instance: n8n Cloud (.app.n8n.cloud)

Workflow: decree content scraping

Waktu kejadian pertama: 26 august 2026, 16:50:28

Mohon bantuannya, terima kasih.

2

Hey @raisa_acc, Welcome to the n8n community!
this isn’t your code, and your return $input.all() test already proves that. n8n support confirmed today that the JavaScript Code node fails on version 2.37.1 and that they’re looking into it. The fix is to update your instance to the latest stable from the admin dashboard, and the person who got that reply updated and posted that it’s working again.

If you can’t update right now, switch the Code node language to Python and you’ll keep running, since it’s only the JavaScript path that’s broken.

Someone hit this a few hours ahead of you and quoted the support reply in full:

3

@raisa_acc This will be fixed in 2.37.2 wich will be available shortly.

4

Since even a minimal Code node (return $input.all();) is timing out, this doesn’t look like a problem with your workflow or code.

The error suggests that the Code node task cannot be assigned to a task runner within the timeout window.

Because you’re using n8n Cloud and the issue affects all Code nodes, it may be a temporary platform-side issue or runner capacity problem.

Could you check the n8n status page and, if the issue persists, contact n8n Cloud support with:

  • Cloud instance URL
  • Workflow name
  • Approximate timestamp of the failed execution
  • Execution IDs (if available)

Are non-Code nodes (HTTP Request, Set, Edit Fields, etc.) still running successfully?