Task request timed out after 60 seconds, please

Questions
1

My n8n flows aren’t working every time they reach the code node. At first, I thought it was just one code node, but I checked the others and it’s happening in all of them that use code as a node. "Task request timed out after 60 seconds
", an error that never appeared before, and I don’t know how to solve it or why this is happening.

Information on your n8n:

  • n8n version: 2.4.6
  • Running n8n via n8n cloud):

image
image740×827 47.5 KB

Is this happening to anyone else? I need help as soon as possible to get the processes working again.

1 Like
2

could you please write in English.so you could help you.

1 Like
3

Olá, @Vinicius_Costa ! Bem-vindos à comunidade n8n.
Isso não é problema no seu código.

Existe um problema conhecido no n8n Cloud em que todos os Code nodes começam a falhar com
Task request timed out after 60 seconds.
O que acontece é que o task runner do workspace fica travado/instável, então qualquer Code node dá timeout, mesmo com código simples.

Outros usuários tiveram exatamente o mesmo e só voltou ao normal depois de reiniciar ou atualizar o workspace:
https://community.n8n.io/t/n8n-cloud-2-0-3-code-nodes-intermittently-fail-with-task-request-timed-out-after-60-seconds/251121

Code nodes are stuck

Como você está no n8n Cloud, você não consegue corrigir o runner manualmente. O que fazer:

  1. Reinicie o workspace (principal)
    Cloud Dashboard → Admin Dashboard → Manage → Restart workspace

Isso já resolveu casos de nodes presos/queued:
https://community.n8n.io/t/code-node-fails-to-get-assigned-executed-every-time/260158

https://community.n8n.io/t/webhook-stays-on-queued-in-the-cloud/214185

  1. Atualize a versão do n8n
    Você está na 2.4.6, então atualize para a versão mais recente pelo mesmo painel. Várias pessoas disseram que o timeout sumiu após o upgrade:
    https://community.n8n.io/t/javascript-code-node-just-times-out/213690

Ou seja: não é seu workflow. É o runner do Cloud. Reinicia primeiro e depois atualiza que normalmente resolve.

English Version :

Hey @Vinicius_Costa

There’s a known n8n Cloud problem where all Code nodes start failing with
“Task request timed out after 60 seconds.”
It happens when the workspace task runner gets stuck or unhealthy, so every Code node times out even with simple code. Here some link that i found of some other users which experienced the same and it was fixed after restarting or updating the workspace:
https://community.n8n.io/t/n8n-cloud-2-0-3-code-nodes-intermittently-fail-with-task-request-timed-out-after-60-seconds/251121

Codes nodes are stuck

By reading your desc. you’re on n8n Cloud and you can’t fix the runner manually. Do this:

  1. Restart the workspace (most important)
    Cloud Dashboard → Admin Dashboard → Manage → Restart workspace (some reference solutions)
    https://community.n8n.io/t/code-node-fails-to-get-assigned-executed-every-time/260158
    https://community.n8n.io/t/webhook-stays-on-queued-in-the-cloud/214185

  2. Update n8n
    You’re on 2.4.6, so upgrade to the latest version from the same panel. Many users reported the timeout disappeared after updating:
    https://community.n8n.io/t/javascript-code-node-just-times-out/213690

So it’s not your workflow, it’s the Cloud runner. Restart first, then update, and it should be resolved.

I tried to translate it, Let me know if this helps.

4

Hey @Vinicius_Costa,

Just to reinforce what @Deepankar shared — this is definitely a known issue with the n8n Cloud task runner getting into a stuck state. The 60-second timeout on Code nodes happens even with simple code when the runner is unhealthy.

**Quick fix priority:**

1. **Restart your workspace** (Cloud Dashboard → Admin Dashboard → Manage → Restart) — this fixes it 90% of the time

2. **Upgrade to latest** (you’re on 2.4.6, latest stable is 2.6.3) — several task runner fixes landed in recent versions

**To prevent this going forward:**

- If you’re running heavy data processing in Code nodes, consider splitting the workload using the “Split in Batches” approach or moving logic to a Function node (which has different execution constraints)

- For long-running operations, you might want to use the HTTP Request node to call an external service instead of processing within the Code node

Hope your workflows are back up and running soon! :rocket:

2 Likes