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!
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.
Thanks for the update and sorry to hear incognito didn’t help either. Since you’ve confirmed it’s not extension-related and the tab becomes unresponsive within 10 seconds, my guess is that this is a platform-side rendering issue with how the flow history loads run records for flows that use Reasoning Groups. You’re right that the content doesn’t appear to be lazily loaded, which means the browser is trying to render the full history at once. Unfortunately, I was not able to find a user-side setting to change how the history loads or to paginate it. I would recommend opening a support ticket (Case management).
Since we have not heard back from you, I’ll go ahead and close/archive this topic. However, if you have any additional questions, feel free to create a new topic in the community and link this discussion for relevant information.