A Power Automate flow would work great for this!

@Ben Linford

@Mike Gillis

This is what we will jump into tonight!

No meeting tonight. Happy Veteran's Day!

No, it's not just your tenant. Microsoft has officially acknowledged on Microsoft Learn (page last updated April 10, 2026) that "the new designer can consume more browser memory on complex flows," and there is a clear wave of independent reports from Feb–April 2026 on the Power Platform Community forums and on Microsoft Q&A describing exactly the symptoms Dustin is seeing, the "Page Unresponsive / Wait / Exit page" dialog, the gray "Aw, Snap!" OOM crash with the blue Reload button, and slow editing and testing, especially on flows that still contain the now-deprecated "Post a message as the Flow bot" Teams action that Microsoft is retiring April 30, 2026 with hard-disable rollout May 18–22, 2026. Microsoft Learn ================== It's a stack of three things piling up at the same time: 1. the new v3 cloud-flow designer holds/leaks memory on complex flows, 2. Chromium tabs have a per-renderer memory ceiling, and 3. the in-flight Office 365 Connectors / Flow Bot retirement is producing "invalid parameter" floods on load that push memory over the cliff on legacy flows. It is a real, broad, Microsoft-side regression made worse by an unrelated deprecation in the same window. ================== Fastest fixes right now: flip the designer to classic (toggle off "New designer" or append ?v3=false to the URL), open the flow in an Edge InPrivate window with no other tabs and no extensions, confirm you're on 64-bit Edge/Chrome, "Save As" the flow without opening the original and edit the copy, and break large flows into child flows. If the offending step is the Flow Bot / Office 365 Connectors action, delete it on the Save-As copy before the page finishes loading.

@Dustin Rocksvold it would have been nice to have you there, Dustin! :) Yeah, I'm actually working on the video now. Cleaning it up, etc.