If you’ve already confirmed this happens even in a brand-new workflow with a minimal Code node, the next step is to escalate with your workspace details.
When you contact them / post for escalation, include:
-
your Cloud workspace URL
-
your n8n version
-
a couple of failing execution IDs + timestamps
-
“Help → About n8n → Copy debug information” (paste it)
This is where you can find more information.
Also worth trying: there are reports where updating n8n Cloud resolved the exact runner timeout (e.g., 2.0.3 → 2.3.6) Here