Most Power Automate Users Don't Know Desktop Flows Can Now Self-Heal When They Break
A new preview feature lets Power Automate desktop flows detect a failing UI action and fix it automatically—no human babysitting required. Most teams are still writing manual error handlers.
01. What It Is
Power Automate for desktop now includes a preview capability called self-healing, powered by Copilot AI. When an automation tries to click a button, tick a checkbox, or interact with a single UI element and can't find it—the classic 'Element not found' error—the AI agent steps in and attempts to locate the correct element and complete the action on its own.
Traditionally, desktop RPA breaks the moment an app updates, a screen shifts, or a button moves slightly. Builders then wrap every action in try/catch blocks, retries, and fragile selectors. Self-healing shifts some of that burden to an AI agent that reasons about the intended target instead of relying only on the exact recorded coordinates or identifiers.
It's important to understand the boundaries: this is a preview feature, it applies only to supported UI and browser automation actions that touch a single UI element, and it only responds to 'Element not found' failures. It does not cover window handling, screen handling, or multi-element actions—so it complements, rather than replaces, your existing error handling.
Why It Matters
UI automations are notoriously brittle, and a single moved button can halt an unattended overnight flow and require a developer to rebuild selectors the next morning. Self-healing can keep flows running through minor UI changes without human intervention, reducing downtime, support tickets, and the maintenance tax that makes many RPA projects expensive to keep alive.
Who Can Benefit
- RPA developers maintaining large libraries of fragile desktop flows
- IT and operations teams running unattended automations overnight
- Businesses on Power Platform premium plans wanting less break-fix maintenance
- Citizen developers who lack the skills to write robust manual error handling
02. Step-by-Step Guide
- 1
Confirm your plan and version
Self-healing requires an organization premium account (no extra cost, but plan-specific) and Power Automate for desktop version 2.66 or higher. Update the desktop app if you're on an older build.
- 2
Enable Copilot in the admin center
An admin must enable Copilot features for Power Platform in the Power Platform admin center. Self-healing depends on these AI capabilities being turned on for your environment.
- 3
Check region and cloud eligibility
Verify your environment is in a supported region. The feature is unavailable in government clouds (GCC, GCC High, DoD) and sovereign clouds, and outside US cloud regions you may need to consent to cross-region data movement.
- 4
Turn on self-healing for your flow
In Power Automate for desktop, enable the self-healing option for the flow. It's optional, so you decide which flows use it—and you can disable it at any time.
- 5
Target the right actions
Apply it to supported UI and browser automation actions that interact with a single element (buttons, checkboxes, etc.). It won't help with window handling, screen handling, or multi-element actions.
- 6
Run attended or unattended—not designer
Self-healing works for both attended and unattended runs, but it does not trigger during designer (test) runs, so validate behavior in an actual attended or unattended execution.
Pro Tips
- Keep it as a safety net, not a replacement: pair self-healing with a lean error-handling strategy for the failure types it doesn't cover.
- Because it only responds to 'Element not found' errors, monitor logs to see when it kicks in—repeated healing on the same action is a signal that your selector needs a real fix.
- Roll it out on a few noncritical flows first to observe how the AI resolves elements before enabling it fleet-wide.
Warnings & Limitations
- This is a preview feature, not general availability—behavior and availability may change, and it isn't recommended for mission-critical production without testing.
- It only handles 'Element not found' errors on single-element UI and browser actions; window, screen, and multi-element actions are not covered.
- Requires an organization premium account, Copilot enabled, and version 2.66+; it won't appear otherwise.
- Not available in GCC, GCC High, DoD, or sovereign clouds, and does not run during designer test runs.
Related Tricks
Most Teams Don't Know Slack Can Now Let You Watch AI Agents Code Live
Slack Code drops Claude, Devin, Copilot, and Vercel agents into dedicated channels where your whole team can watch diffs, preview output, and ship—without ever leaving Slack.
Notion Just Let AI Agents Edit Your Databases Directly — No Zapier Needed
Notion's new External Agents API turns Claude Code, Cursor, and other AI tools into @-mentionable teammates that read and write to your databases in real time. The automation middleman is gone.
Most Zapier Users Don't Know Their AI Can Edit Their Database Straight From Chat
Zapier Tables can now act as a live data layer your AI agent reads and updates in real time—so Claude or ChatGPT can add, edit, and query rows without you ever opening the database.