Power Automate Stuck in Classic Designer: How to Force the New Designer UI

Microsoft has been aggressively rolling out the "New Designer" for Power Automate (cloud flows), offering a more modern, Copilot-integrated experience. However, many users find themselves stuck in the Classic Designer mode, with the toggle switch either missing, greyed out, or failing to save their preference.

If you are trying to access the latest features but keep getting reverted to the legacy interface, follow these troubleshooting steps to fix the Power Automate designer UI.

1. Use the "v3" URL Parameter (The Quick Fix)

If the toggle switch at the top right of your screen isn't working, you can manually force the New Designer by modifying the browser URL. This bypasses the stored cookie preference.

• Open your flow in the Classic Designer.
• Look at the URL in your browser address bar. It likely ends in ../details or ../edit.
• Add ?v3=true to the end of the URL (e.g., .../flows/GUID/edit?v3=true).
• Press Enter to reload the page in the modern interface.

2. Clear Browser Cache and Local Storage

Power Automate stores your designer preference in the browser's Local Storage and cookies. If these files become corrupted, the "Try the new designer" toggle will fail to function.

1. Press F12 to open Developer Tools in Edge or Chrome.
2. Go to the Application tab.
3. In the left sidebar, expand Local Storage and select https://make.powerautomate.com.
4. Search for keys containing "designer" or "v3" and delete them.
5. Refresh the page and try the toggle again.

3. Check Environment Region and Preview Features

The New Designer is rolled out in waves based on your Power Platform Environment Region. Some "Government Community Cloud" (GCC) or older sovereign regions may not have full access to the New Designer yet.

• Verify with your tenant admin if "Preview Features" are enabled for your environment.
• Check if your environment is set to a "Recommended" release cadence rather than a "Late" one in the Power Platform Admin Center.

4. Unsupported Triggers and Actions

In some cases, Power Automate will automatically revert to Classic Designer if your flow contains specific legacy connectors or complex "Split On" settings that the New Designer does not yet support. If the New Designer cannot render a specific action, it will force the legacy view to prevent data loss or flow corruption.

5. Browser Extensions and Ad-Blockers

Heavy-duty ad-blockers or "Privacy" extensions can sometimes block the scripts required to load the React-based New Designer. Try opening Power Automate in an Incognito/InPrivate window. If the New Designer works there, a browser extension is likely the culprit.

Why Does the Toggle Keep Switching Back?

Microsoft occasionally disables the New Designer temporarily when they detect a high telemetry error rate for a specific tenant or region. If you find the New Designer works for 10 minutes and then reverts, check the Power Platform Service Health dashboard for ongoing designer outages.

Conclusion

Being stuck in the Power Automate Classic Designer is usually a result of a cached browser preference or a specific URL state. By using the v3=true parameter or clearing your site data, you can usually force the modern UI. However, keep in mind that for very complex flows with legacy logic, the Classic Designer remains the most stable environment for deep troubleshooting.