Power Automate run history behavior changes based on browser cookie settings.
If third‑party cookies in the browser are allowed for make.powerautomate.com:
- Run details open inline
- No left-side details pane
- Links open in the same tab
If third‑party cookies are blocked OR make.powerautomate.com is removed from
“Allowed to save cookies”:
- Classic run details viewer loads
- Details appear in the left-side pane
- URL format changes to /solutions/.../flows/.../runs/...
This behavior is undocumented and forces users to weaken browser privacy
or lose basic debugging usability.
Power Automate – Modern Run History Fallback Behavior Observed behavior
The redirect from the modern run history interface to the classic viewer appears to be a system‑level design behavior, not something controlled by users or admins. The modern experience relies on browser storage and cross‑site cookies to keep session state and UI context.
Root cause
When third‑party cookies are blocked or browser settings like “Prevent Cross‑Site Tracking” are enabled, the modern Fluent UI shell cannot maintain its session. Instead of fully failing, Power Automate automatically falls back to the classic run history viewer.
Current limitations
No admin control: There is no per‑user or per‑tenant setting in the Power Platform Admin Center to force the modern UI or override the cookie requirement.
Client‑side dependency: The behavior depends entirely on local browser privacy settings.
Recommended action
This should be treated as a UX regression. The right next step is to raise this through Microsoft support or the Power Automate Feedback portal, with the goal of providing a modern run history experience that does not depend on third‑party cookies and aligns with current browser privacy standards.
✅ If this answer helped resolve your issue, please mark it as Accepted so it can help others with the same problem.
👍 Feel free to Like the post if you found it useful.
Was this reply helpful?YesNo
Under review
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.