N8N (cloud) UI freezes when opening HTTP or Code node

[weareturnone]

Bug Description

Whenever I open the HTTP node or a code node in a workflow that uses the DeepGram API, the UI freezes and becomes unresponsive. Then the browser times out the session and need to reload the page. This happens consistently and it does not matter which canvas I use.

To Reproduce

Create a HTTP request node with a POST request to the DeepGram API get a response...

Expected behavior

To be able to open the Node in the UI and interact with the UI

Operating System

n8n Cloud

n8n Version

1.68.0

Node.js Version

20.18.0

Database

SQLite (default)

Execution mode

main (default)

[Joffcom]

Hey @weareturnone,

We have created an internal ticket to look into this which we will be tracking as "GHC-494"

[netroy]

Is this with data on the nodes, or is this happening for you even before you execute the workflow?

[weareturnone]

Is this with data on the nodes, or is this happening for you even before you execute the workflow? @netroy

This only happens after a execution/ the HTTP and/ or code node have executed. Tried it in Chrome and Arc and Safari, also after restarting and updating the hosted n8n cloud instance as well as my mac.

[netroy]

Can you please check how much data the http request returns? This sounds like an issue of too much data being loaded into the UI.

Another thing you could try is to open the Node details view, switch to Table or JSON view, instead of the Schema view, and then try executing the workflow.
The schema view is currently not optimized for performance, but that will be fixed in the next release.

[weareturnone]

Trying to check it but even when looking at the "executions" the UI freezes/ becomes unresponsive. Not sure how to otherwise find it. In the browser dev tools, "network" shows about 40kb of (disk cache) usage.

When waiting for a minute or two (if the browser doesn't kill the session), the node becomes responsive again but when you then click on a UI element, for example to check the Json output, it freezes again.

I guess it might be a RAM issue on N8N Cloud? I am on the starter plan and have no issues running locally. On the other side, this workflow was working fine in the weekend with the same input files.

For some context. The workflow gets a audio file from google drive and then sends the binary file to DeepGram API. The DeepGram HTTP node freezes after completion as well as a code node that processes the output (transcript) from DeepGram (does some formatting). Other nodes on the canvas stay responsive, even after multiple "loops" when the flow is triggered with 5+ audio files (200MB+ of audio files) -> Tried this out to see if that would crash everything or show some more info.

[netroy]

Would it be possible for you to create and share a minimal workflow with which you can consistently reproduce this issue? that would help significantly in narrowing down what the issue might be.

[MiloradFilipovic]

Hey @weareturnone
I tried reproducing this with a pretty large audio file (24mb) and can see that UI is slow but as @netroy pointed out it is most likely caused by loading large data in UI, especially using the schema view.
Can you try previewing the output in Table view? The trick here is to open HTTP node and switch to table view, once you switch it should remember your choice and always open in Table mode:

Screen.Recording.2024-11-27.at.14.15.33.mov

If Table view is usable for you here, then the problem indeed is in slow Schema view for large data, something we are already working on. I tried the same workflow with the new schema view and didn't see any lag there.

[weareturnone]

unfortunately the issue also persists on table and json views. I do not have the issue when self hosting n8n on a digital ocean or hetzner vps though.

…

Message ID: ***@***.***>

[janober]

Fix got released with [email protected]

[netroy]

@weareturnone Closing this as completed. But please let us know if the updates did not address the performance issue for you 🙏🏽