Quick/Flows - viewing history has CPU @100% (chrome tab)

I open the history of a flow, and the view is only building up slowly, and hangs so much that navigation is impossible (including scrolling).

Checking the Chrome Task Manager, the “Tab: Quick - Flows” has no Memory footprint, but hangs at 100-120 CPU usage compared to 0.0–3.5 of other tabs

Hi @dmjk and welcome to the community!

That sounds like a rendering issue. My guess is that this is likely the flow history trying to load and display a large number of run records at once, which overwhelms the browser tab. I would recommend you try opening the flow history in an incognito/private window with extensions disabled. Browser extensions can sometimes conflict with heavy DOM rendering and spike CPU usage. I would also try different browsers to see if it’s Chrome-specific.

Hope this helps and feel free to keep us updated with any new questions or developments you have!

Hi @WLS-Cesar and thank you for your comment!

In our enterprise environment we are quite limited with respect to browser choice or extensions, so the setup is pretty lean already. Trying in incognito mode lead to the same issues, i.e. notification that the tab has become unresponsive after ~10s.

What the flow does, is employ a couple of steps in a Reasoning Group. From your answer I gather that content it not lazily loaded, which then overwhelms the tab, to the point that I can not even download the history via PDF or similar.

Since this flow should be used by a wider user basis, I really need to find a solution to the issue.