Hi - i’m getting an error on all my n8n workflows that contains a “code” node. They are all timing out after 60 seconds. Nothing changed. All of a sudden, everything is timing out.
Can you please explain how to fix this?
Thanks
1 Like
Hi @Benjamin_Elbaz Welcome!
Can you give us more information about your n8n instance? version?
the 60s timeout is usually your task runner not connecting to the broker or the broker itself timing out. if youre self-hosted, check your runner container is actually connected and check the broker logs — usually shows OOMkilled or connection timeout there. simple code without loops shouldnt ever hit 60s, so my guess is the runner isnt responding instead of your actual code timing out. whats your setup, self-hosted or cloud? and does it happen even on simple code or just complex workflows?
I updated the n8n version of my instance and it’s working now - but how come we have 0 warnings about those kind of things and n8n allows this to happen. 100s of workflows failed
glad it’s fixed. silent failures on version upgrades are rough, n8n really should log something when a component breaks compatibility. if you havent filed a github issue, the before/after version info would help the team reproduce it.