Hi everyone,
I’m experiencing a critical issue with n8n Cloud where my Python Code node stopped working abruptly, even though I did not update anything in my workflows or environment.
The Python script I’ve been running for a long time without changes suddenly fails or doesn’t complete at all. I’m on the paid n8n Cloud plan and there was no manual update from my side, but this behavior started happening recently.
Details of the problem:
- My workflow includes a Python Code node that was working for months without issues.
- Recently, it either fails with errors related to imports/access, or gets stuck “executing” indefinitely.
- I didn’t change the code or workflow — it just stopped working all of a sudden.
- This breakage happened without any visible version update in my workspace.
I suspect it’s related to the recent backend rollout of Python (native) runner and task runners in n8n Cloud. According to documentation and community reports, the legacy Pyodide Python support has been deprecated and replaced with a native Python runtime via task runners, which introduces breaking changes. Existing scripts that depended on legacy behavior may now fail because of changes in variable access, import restrictions, and runner behavior.
This has impacted my production workflows seriously, and I haven’t touched the script itself. Has anyone else on the cloud plan seen similar sudden Python Code node failures without a local update?
Thanks!