Task runner timeout on all Code nodes — even brand new/empty workflows Mensaje:

Questions
1

Instance: cristiandt91.app.n8n.cloud
Plan: Cloud trial

I’m getting “Task request timed out after 60 seconds — the task runner is currently down, or not ready, or at capacity” on every Code node execution.

I’ve confirmed this is NOT specific to one workflow:

  • My main production workflow (30+ nodes) fails consistently on any Code node
  • I created a brand new, empty workflow with a single Code node returning a hardcoded string (“hola mundo”) — it also gets stuck in “Running” and never completes
  • status.n8n.cloud shows all systems operational
  • I’ve tried unpublishing/republishing the affected workflow — no change

This matches other reports in this forum with the same exact error (e.g. “Task runner timeout on n8n Cloud - Code nodes failing for a week”, “Urgent: Task Runner Timeout After Account Reactivation”) where the resolution required n8n support to reprovision or reset TaskRunners for the affected account.

Could someone check the TaskRunner provisioning for my instance?

2

Hi @Cristian_Cabezas Welcome!
A “hola mundo” Code node timing out in a brand new workflow means the TaskRunner for your Cloud instance is stuck, which is instance-side and only n8n’s team can reset, so no one in the community can reprovision it from here.
Email help@n8n.io with your instance URL (cristiandt91.app.n8n.cloud), a failed execution ID and its timestamp, and the exact error, and ask them to reset or reprovision the TaskRunner for your instance. Some earlier cases were resolved by them disabling TaskRunners on the account.
See this: