Hi all,
I’m running n8n self-hosted via Docker on Unraid (n8nio/n8n:latest), currently reporting version 1.103.2 (checked with n8n --version inside the container).
Problem:
- Any workflow with a new Code node (not legacy Function) hangs indefinitely on “Executing node…” — even with the most basic, valid code.
- Example (set to “Run Once for All Items”, input is
[{}]):
javascript
CopyEdit
return $input.all().map(item => ({
json: { ...item.json, myNewField: 1 }
}));
- No errors or output, just hangs.
- Set node expressions work fine for the same logic.
- I’ve tried many variations (map, for loop, direct return) — same result.
- Workflow/logs show node “started” but never “finished”, and workflow eventually fails on a previous node.
What I’ve tried:
- Minimal reproduction (just a trigger and Code node with above code).
- Both
n8nio/n8n:latestandn8nio/n8n:stabletags. - Restarted container, checked logs — no stack traces or explicit errors.
Questions:
- Is this a known bug with the new Code node in my version (1.103.2 / “latest”)? Has it been fixed in more recent releases?
- Is there any reliable workaround besides using Set node expressions?
- (Tag/Version question):
Is there any difference between the version I see inside the container and what “latest” should be? Should I be using a specific version tag for best stability?
What’s the recommended upgrade path for Unraid/Docker users?
Thanks for any insights—this issue is really blocking my workflow automation!