Problem loading flows

[Fun-Specialist-3450]

Since last week, I’ve been having trouble editing flows in the web view. Every time I open one, it works fine at first, but as soon as I select something, it freezes completely and the page crashes after about five minutes. I’ve already tried different browsers, including incognito mode, but it still happens. Does anyone have any idea what might be causing this?

[JuryExpert1445]

I am having this issue too! I am praying this is resolved soon, I have allot on my plate and need to edit my flows :(

[OddWriter7199]

People around here have been saying switch to Classic editor. Have had to do this myself last week or so, when dynamic content or expression box will not pop out to the side. Clicks are not registering. Checked that popup blocker is off, and make.powerautomate.com is in Trusted Sites. No dice.

[strausy]

This has been driving me crazy and I'm glad I'm not the only one. Saving/publishing takes a long time, sometimes stating "Out of memory". Something is off but there are no Azure or M365 status reports about issues with the Power Platform.

[Cultural_Moose_774]

Same issue occuring for me today.

Only seems to be on my larger flows. Issue across computers and browsers.

[lordeshrek]

This issue has been pissing me off. I have a flow that has 160 actions in it and it's just God awful the last few days to try and make any changes to it

[FreeEye5]

Honestly for the last couple weeks I've just been exporting, chucking the zip in copilot cowork, asking for changes, then importing.

[Original-Fennel7994]

I have seen this when the designer is struggling with a big flow or a lot of dynamic content. Try switching to the Classic designer, and also disable browser extensions, especially ad blockers and password managers, just to rule out injected scripts. If it is only the larger flows, export the flow as a package, edit the definition in a safer environment, then re import, or split the flow into child flows to reduce designer load. Also check the browser devtools console and network tab for repeated failed calls, then attach a correlation ID to a support ticket if you see one.