Describe the problem/error/question
In the Code Node, JavaScript execution does not complete and remains stuck in a “processing” state.
This is exactly the same issue described in the following community threads:
We are running n8n version 1.93.0 on GKE.
Despite reviewing the above resources, we have not found a working solution.
As a test, we ran the same workflow using Docker Compose on macOS, and the JavaScript in the Code Node executed successfully.
We also upgraded to n8n version 1.97.1, and again, it worked on macOS but not on GKE.
Additionally, when switching the Code Node to Python, it behaves inconsistently on GKE.
After reloading the browser, the Python node sometimes runs successfully once, but subsequent executions often fail.
Interestingly, some Python Code Nodes continue to work without issue.
Since we are using the same Docker image on both macOS and GKE, we are unsure what could be causing the issue on GKE.
Any help or guidance would be greatly appreciated.
What is the error message (if any)?
Nothing(Python Below)
LogMessage(container log)
-
Main
2025-06-13T06:17:17.479Z | debug | Stopped flushing timer {“scopes”:[“insights”],“file”:“insights-collection.service.js”,“function”:“stopFlushingTimer”} -
Worker(container log)
2025-06-13T06:17:17.605Z | info | Worker started execution 466 (job 439) {“scopes”:[“scaling”],“executionId”:“466”,“jobId”:“439”,“file”:“job-processor.js”,“function”:“processJob”}
2025-06-13T06:17:17.615Z | debug | Execution ID 466 will run executing all nodes. {“executionId”:“466”,“file”:“manual-execution.service.js”,“function”:“runManually”}
2025-06-13T06:17:17.616Z | debug | Workflow execution started {“workflowId”:“dTEUAIh9VFwZTgGk”,“file”:“logger-proxy.js”,“function”:“exports.debug”}
2025-06-13T06:17:17.616Z | debug | Executing hook (hookFunctionsPush) {“executionId”:“466”,“pushRef”:“zl4sshgm3p”,“workflowId”:“dTEUAIh9VFwZTgGk”,“file”:“execution-lifecycle-hooks.js”}
2025-06-13T06:17:17.617Z | debug | Start executing node “When clicking ‘Execute workflow’” {“node”:“When clicking ‘Execute workflow’”,“workflowId”:“dTEUAIh9VFwZTgGk”,“file”:“logger-proxy.js”,“function”:“exports.debug”}
2025-06-13T06:17:17.618Z | debug | Executing hook on node “When clicking ‘Execute workflow’” (hookFunctionsPush) {“executionId”:“466”,“pushRef”:“zl4sshgm3p”,“workflowId”:“dTEUAIh9VFwZTgGk”,“file”:“execution-lifecycle-hooks.js”}
2025-06-13T06:17:17.618Z | debug | Running node “When clicking ‘Execute workflow’” started {“node”:“When clicking ‘Execute workflow’”,“workflowId”:“dTEUAIh9VFwZTgGk”,“file”:“logger-proxy.js”,“function”:“exports.debug”}
2025-06-13T06:17:17.618Z | debug | Running node “When clicking ‘Execute workflow’” finished successfully {“node”:“When clicking ‘Execute workflow’”,“workflowId”:“dTEUAIh9VFwZTgGk”,“file”:“logger-proxy.js”,“function”:“exports.debug”}
2025-06-13T06:17:17.619Z | debug | Executing hook on node “When clicking ‘Execute workflow’” (hookFunctionsPush) {“executionId”:“466”,“pushRef”:“zl4sshgm3p”,“workflowId”:“dTEUAIh9VFwZTgGk”,“file”:“execution-lifecycle-hooks.js”}
2025-06-13T06:17:17.620Z | debug | Start executing node “Code” {“node”:“Code”,“workflowId”:“dTEUAIh9VFwZTgGk”,“file”:“logger-proxy.js”,“function”:“exports.debug”}
2025-06-13T06:17:17.620Z | debug | Executing hook on node “Code” (hookFunctionsPush) {“executionId”:“466”,“pushRef”:“zl4sshgm3p”,“workflowId”:“dTEUAIh9VFwZTgGk”,“file”:“execution-lifecycle-hooks.js”}
2025-06-13T06:17:17.621Z | debug | Running node “Code” started {“node”:“Code”,“workflowId”:“dTEUAIh9VFwZTgGk”,“file”:“logger-proxy.js”,“function”:“exports.debug”}
2025-06-13T06:17:17.622Z | debug | Published pubsub msg: relay-execution-lifecycle-event (executionStarted) {“scopes”:[“scaling”,“pubsub”],“msg”:“relay-execution-lifecycle-event”,“channel”:“n8n.commands”,“type”:“executionStarted”,“executionId”:“466”,“file”:“publisher.service.js”,“function”:“publishCommand”}
2025-06-13T06:17:17.622Z | debug | Published pubsub msg: relay-execution-lifecycle-event (nodeExecuteBefore) {“scopes”:[“scaling”,“pubsub”],“msg”:“relay-execution-lifecycle-event”,“channel”:“n8n.commands”,“type”:“nodeExecuteBefore”,“executionId”:“466”,“file”:“publisher.service.js”,“function”:“publishCommand”}
2025-06-13T06:17:17.623Z | debug | Published pubsub msg: relay-execution-lifecycle-event (nodeExecuteAfter) {“scopes”:[“scaling”,“pubsub”],“msg”:“relay-execution-lifecycle-event”,“channel”:“n8n.commands”,“type”:“nodeExecuteAfter”,“executionId”:“466”,“file”:“publisher.service.js”,“function”:“publishCommand”}
2025-06-13T06:17:17.623Z | debug | Published pubsub msg: relay-execution-lifecycle-event (nodeExecuteBefore) {“scopes”:[“scaling”,“pubsub”],“msg”:“relay-execution-lifecycle-event”,“channel”:“n8n.commands”,“type”:“nodeExecuteBefore”,“executionId”:“466”,“file”:“publisher.service.js”,“function”:“publishCommand”}
→ wait until timeout
When switching to Python, it usually results in an error, but reloading the browser sometimes allows it to run successfully once.
- Browser Log
Error: JsException: ExpressionError: Referenced node is unexecuted at PythonSandbox.getPrettyError (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-nodes-base@file+packages+nodes-base_@[email protected]_asn1.js@5_12b981d6b49d407a163f4d5244314033/node_modules/n8n-nodes-base/nodes/Code/PythonSandbox.ts:101:11) at PythonSandbox.runCodeInPython (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-nodes-base@file+packages+nodes-base_@[email protected]_asn1.js@5_12b981d6b49d407a163f4d5244314033/node_modules/n8n-nodes-base/nodes/Code/PythonSandbox.ts:85:15) at PythonSandbox.runCodeAllItems (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-nodes-base@file+packages+nodes-base_@[email protected]_asn1.js@5_12b981d6b49d407a163f4d5244314033/node_modules/n8n-nodes-base/nodes/Code/PythonSandbox.ts:46:27) at ExecuteContext.execute (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-nodes-base@file+packages+nodes-base_@[email protected]_asn1.js@5_12b981d6b49d407a163f4d5244314033/node_modules/n8n-nodes-base/nodes/Code/Code.node.ts:155:14) at WorkflowExecute.runNode (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-core@[email protected][email protected][email protected]_/node_modules/n8n-core/src/execution-engine/workflow-execute.ts:1185:9) at /usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-core@[email protected][email protected][email protected]_/node_modules/n8n-core/src/execution-engine/workflow-execute.ts:1534:27 at /usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-core@[email protected][email protected][email protected]_/node_modules/n8n-core/src/execution-engine/workflow-execute.ts:2098:11
Please share your workflow
Share the output returned by the last node
Not End
Information on your n8n setup
- n8n version: 1.93.0 → 1.97.1(Upgrade but still error)
- Database (default: SQLite): Postgres
- n8n EXECUTIONS_PROCESS setting (default: own, main): main
- Running n8n via (Docker, npm, n8n cloud, desktop app): Docker
- Operating system: Container-Optimized OS with containerd(GKE Node)