After opening the cloud flow and making some changes, it leads to no enough memory scree

(0) Share

Report

Posted on by UD-10041256-0

I am using microsoft edge as browser. When i open my solution, launch the flow and make some changes.I get this screen as no enough memory.Why is this happening? I tried to clear my cache,tried in different browsers and kept very minimal number of tabs. Please tell me about the solution for this. Thanks

Categories:

Building flows

I have the same question (0)

All responses (3)

Answers (0)

Sort by

David_MA 14,360 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!
Some questions:

How much RAM does your computer have?

Have you tried rebooting your computer?

Have you tried clearing your browser cache?

Have you tried doing what is noted in the error message and closed other tabs and programs?

If you have sufficient memory on your computer, clearing the cache would be my first thing to try.

Was this reply helpful? Yes No
Sunil Kumar Pashikanti 2,031 Moderator on at

Like (0)

Report
Copy link

Link copied!
Hi @UD-10041256-0,

This is a known issue with the Power Automate web designer, not a fault with your browser or computer hardware.

Why it happens:
Even if your computer has plenty of RAM, browsers (Chrome/Edge) place an internal limit on how much memory a single tab can use (usually around 4GB). The Power Automate designer has a "memory leak", every time you edit an action or expression, it claims more memory but doesn't fully release it. Eventually, the tab hits that internal limit and crashes, even if your system still has 90% of its memory free.

A more powerful computer doesn't prevent this; it only slightly delays it.

What actually helps:

Save and Refresh: This is the only way to "empty the bucket" and reset the tab's memory usage. Refresh every 30–60 minutes during heavy editing.

Split Large Flows: Use Child Flows to reduce the "weight" of a single designer session.

Toggle Designers: If the New Designer is unstable for a complex flow, switching to Classic can sometimes offer better stability.

Summary: This is a limitation of the Power Automate UI architecture. Regular refreshing is currently the most effective workaround.

Ref:

https://learn.microsoft.com/en-us/power-automate/classic-vs-modern-designer

Was this reply helpful? Yes No
Suggested answer

Ahash 2 on at

Like (0)

Report
Copy link

Link copied!

This is not a hardware problem but a product problem and cannot be resolved with the suggested methods. I tried it with Firefox which doesn't have as much RAM restriction as Chrome and the same Flow that takes ~2000 MB RAM (in old designer) went over ~11000MB RAM.

There seams to be a memory leak issue in the code. Apparently this issue is known by Microsoft and is currently being investigated at the time of writing: https://admin.powerplatform.microsoft.com/support/knownissues/6297582

A workaround would be to use the old Designer if that works for you. Unfortunately the Flow can be in a state where an Edit in the new Designer is required, in that case you'd have to wait until the issue gets fixed.

Was this reply helpful? Yes No