🚨 JavaScript Code Node Timeout in v1.98.1 — Works Fine in v1.97.1

[vineetdpnd]

Bug Description

After upgrading to n8n@1.98.1, all executions using the Code Node (JavaScript language) stop responding and eventually time out — even with basic or minimal logic inside. This issue is not present in version 1.97.1, where the same workflows run perfectly.

Notably, Python language execution in the Code Node continues to work normally, indicating this is specific to the JavaScript node execution in 1.98.1.

System memory is not a constraint — we have 30GB+ of free memory on the host, and no other performance issues are observed.

To Reproduce

1. Upgrade from v1.97.1 to v1.98.1
2. Create a new workflow with a Code Node using:

return [ { json: { test: $now } } ];

3. Execute the node

4. Observe that the node hangs indefinitely or times out with no result

5. Roll back to v1.97.1 → same node executes correctly.

Expected behavior

The JavaScript Code Node should:

Execute even basic JavaScript code without issue

Return a valid output object (as it did in previous versions)

Operating System

Ubuntu 24.04.2 LTS

n8n Version

1.98.1

Node.js Version

v22.14.0

Database

PostgreSQL

Execution mode

main (default)

[Joffcom]

Hey @vineetdpnd,

Thank you for reaching out! We’ve received your issue and are looking into it. To help us track this internally, we’ve created a Linear ticket with the reference: "GHC-2664".

We’ll keep you updated as we make progress, but if you have any additional details or context to share, feel free to add them here - it’s always helpful!

Thanks for your patience and for bringing this to our attention.

[Joffcom]

Thanks for reporting this issue! We’ve attempted to reproduce the problem, but unfortunately, we weren’t able to replicate it. It’s possible there was some environmental or other variable that prevented us from seeing the same behavior.

This is what I am seeing when following your instructions, Although I am on 1.98.2 so it could be that it was fixed but I am not aware of anything that would have impacted this.

[vineetdpnd]

@Joffcom We deploy n8n using Docker. Please let us know if it would be helpful to share our docker-compose.yaml setup — happy to provide it for debugging.

We will also try upgrading to 1.98.2 and report back if the issue persists in that version or if it's resolved.

Thanks for your support

[rlegall-eness]

Hi, it seems that we've the same issue as @vineetdpnd.

We have two n8n instances on the same server. One in regular mode and the other one in queue mode. The code node in the regular one in 1.98.2 works perfectly but, in the queue one in 1.98.2, the same code node, with just a simple return, seems to hang indefinitely.

Thanks.

[Joffcom]

Most unusual, I am also running in queue mode with no issues. Are you both using task runners? It would be handy if you could both share the env options you have set (removing any sensitive values).

[mliga666]

Same problem, reverting to 1.97.1 solved

[Joffcom]

@mliga666 same question... what env options do you have set? We will need to work out the pattern for this one. I have tried on self hosted in queue mode and on cloud with no issues