Fix Power Automate Designer in Classic Mode: Clear Cookie and Enable Modern UI

by

Summary

The Power Automate Cloud flow editor can become stuck in Classic Designer mode, hiding the toggle that normally switches to the Modern Designer. Adding ?v3=true to the URL often forces the new UI, but when that fails the underlying cause is usually a cached user setting or tenant‑level feature flag that forces the legacy view.

Root Cause

  • User‑level UI preference stored in the browser cache – the platform reads a cookie (uiMode) on page load.
  • Tenant feature flag (EnableModernDesigner) may be disabled for the user’s environment.
  • Mixed‑mode authentication token that omits the v3 claim, causing the backend to serve the classic UI.
  • Aggressive CDN caching of the flow list page, serving an outdated HTML bundle that lacks the toggle.

Why This Happens in Real Systems

  • Enterprises often lock UI features via Azure AD Conditional Access or Power Platform admin settings to avoid breaking legacy automations.
  • Browser extensions or privacy settings scrub cookies, removing the UI preference flag.
  • Service updates roll out the Modern Designer gradually; users on older rollout rings see the classic view until the rollout completes.
  • Multi‑tenant SaaS platforms must preserve backward compatibility, so they fall back to classic UI when any mismatch is detected.

Real-World Impact

  • Reduced productivity – users spend minutes hunting for the missing toggle.
  • Incorrect debugging – classic designer shows fewer visual cues, leading to missed errors.
  • Training gaps – new hires are taught the modern UI, causing confusion.
  • Support overhead – escalations to Microsoft support increase ticket volume.

Example or Code (if necessary and relevant)

# Clear the UI mode cookie and force Modern Designer
$uri = "https://flow.microsoft.com"
$cookie = New-Object System.Net.Cookie("uiMode","modern",$null,$uri.Host)
$web = New-Object System.Net.WebClient
$web.Headers.Add("Cookie", $cookie.ToString())
$web.DownloadString("$uri/manage/flows")

How Senior Engineers Fix It

  • Clear the UI‑mode cookie or use an incognito window to force a fresh fetch.
  • Verify the tenant feature flag in the Power Platform admin center:
    • Settings → Environments → Environment name → Features → enable Modern Designer.
  • Add the v3=true parameter after any existing query string (e.g., .../flows?tenantId=xxx&v3=true).
  • Flush CDN cache for the tenant by triggering a “Refresh UI” from the admin portal.
  • If the issue persists, open a support ticket with the correlation ID from the browser dev‑tools network tab.

Why Juniors Miss It

  • Focus on the UI: they look for a visual toggle instead of checking hidden cookies or admin settings.
  • Assume a bug: they open a ticket without verifying simple cache‑clear steps.
  • Lack of environment knowledge: they don’t know that feature flags can be scoped per tenant or user.
  • Limited debugging tools: juniors may not use browser dev‑tools to inspect cookies or request headers.

Leave a Comment