Hi, Code node executions are timing out on my n8n Cloud instance,
even on a brand new empty workflow with a trivial Code node
(return [{json: {ok: true}}]).
Instance URL: [ laabs.app.n8n.cloud](https://laabs.app.n8n.cloud/)
Failed execution ID: ID#4
Timestamp: Aug 25, 21:56:07
Error: Task request timed out after 60 seconds — your Code node
task was not matched to a runner within the timeout period.
Could someone help reprovision/reset the Task Runner for my instance?
Hi @Laurent_Abiven Welcome!
Nobody here can reprovision a Cloud task runner, and the error is n8n telling you the runner is down, not ready, or at capacity, which your empty-workflow reproduction already rules out as anything in your code. The Code node timeout is an environment variable that Cloud does not expose, so there is nothing to raise on your side either.
Your one self-service lever is the admin dashboard, where a version change redeploys the instance. If that does not clear it, send help@n8n.io the instance URL, execution ID#4 and the 21:56:07 timestamp you already have, because a runner slot that never came up has to be reset on their side.
This looks like a Task Runner availability issue rather than a problem with the workflow or Code node itself. The fact that the same timeout occurs in a completely new workflow with such a simple return statement is a strong indication that the runner is either unavailable, not ready, or unable to accept the task.
I’ve seen similar reports where all Code nodes fail with the same 60-second runner timeout, even though other workflow nodes continue to execute normally. Hopefully, the n8n team can check the runner status for the affected Cloud instance and reprovision it if necessary. Providing the execution ID and timestamp, as you have done, should also make troubleshooting easier. Hopefully this gets resolved quickly.
This will be fixed in 2.37.2 which will be available soon