Hello, first time running into this issue as an admin in our n8n instance and across all workflows, our JavaScript code nodes are failing with timeout errors. regardles # of items being passed to the code or what that code does. Google highlighted the need to restart our task runner. Is there any way to do this without the support’s involvement?
I already logged a support ticket for this
Thanks, we are on cloud w/ business sub, we are on an older version, would updating help restart the cloud runner?
Hi @Tyler_Chandler_de_Fa, welcome!
Although timeouts are normal in code nodes on n8n cloud instances, if the timeouts are hitting in almost every code, the best possible move currently is to reach out for support, as you are on a business plan you will get priority support.
welcome to the n8n community @Tyler_Chandler_de_Fa
Did this start suddenly across all workflows at the same time? If yes, it’s very likely an instance-level issue. Since you’re on n8n Cloud Business and already opened a ticket, I’d include one minimal workflow with a Code node like return $input.all();, plus the execution ID, timestamps, and the exact timeout error so support can trace it quickly.
If this is blocking production, a temporary workaround is to move the JavaScript logic out of the Code node and run it in an external service/webhook, then call it from n8n with HTTP Request. For very simple logic, replacing the Code node with native nodes like Set/Edit Fields, IF, Switch, Merge, or Item Lists may also avoid the affected runner path until support fixes the instance-level issue.