TL;DR: Power Automate now uses AI to automatically recover desktop flows when UI elements change — without a developer rewriting the bot. This self-healing capability is now available for organisation premium accounts and can cut RPA maintenance time dramatically.
If you have built desktop flows using Power Automate’s RPA capabilities, you know the drill.
Someone updates an application. A button moves slightly. A form field is renamed. The resolution on an unattended machine changes. Your bot runs overnight, hits an “Element not found” error at step 3, and the whole automation fails.
Traditional RPA is fragile by design. Self-healing changes that.
If you are a Power Platform maker, an automation developer, or an IT administrator managing unattended bot infrastructure, here is how Power Automate’s AI self-healing works — and why it matters for your operations.
Official Website: Self-healing for desktop flows — Microsoft Learn
What is AI self-healing in Power Automate?
What problem does it solve?
Standard desktop flows (RPA — Robotic Process Automation) interact with applications by clicking on specific UI elements: buttons, text boxes, dropdowns, checkboxes. These interactions are recorded by identifying elements through attributes like their ID, label text, class name, or on-screen position.
When an application updates — even just a visual refresh — those attributes can shift. A button that was called Submit_Button_01 might become SubmitBtn after an update. The position of a form field might move three pixels to the right after a layout change. To a traditional RPA bot, these tiny changes are invisible. It looks for the exact element it was taught to find, fails to locate it, and stops.
Self-healing is the AI layer that sits between a failed element lookup and a full automation error.
How does AI self-healing work?
When a desktop flow encounters an “Element not found” error, the self-healing agent activates as a fallback before the flow stops.
The agent uses a combination of three techniques to re-identify the missing element:
- Computer vision — Analyses the live application screen to find elements that visually resemble what the bot was looking for.
- Fuzzy matching — Compares element attributes with a degree of tolerance, matching elements that are close but not identical to the recorded attributes.
- Relative positioning — If the element’s neighbours on screen are still identifiable, the agent uses their position to infer where the target element has moved to.
If the agent successfully identifies a likely match, it completes the action on that element and logs the recovery. The flow continues without human intervention.
What is the error handling sequence?
Power Automate evaluates failed actions in a specific order. Self-healing sits as the second layer:
- Retry policy — The action is retried a defined number of times at set intervals.
- AI self-healing — If retries fail, the self-healing agent attempts to locate and interact with an alternative matching element.
- Rule-based handling — If self-healing also fails, configured rule-based fallbacks run (e.g., set a variable, run a subflow to notify a human).
- Final result — The flow either continues past the error or throws an error depending on your error handling configuration.
What else is new in Power Automate for desktop?
Beyond self-healing, September and October 2026 brought two more significant improvements for desktop flow makers.
Native Scheduling in Automation Center
Previously, scheduling an unattended desktop flow required creating an intermediate cloud flow just to trigger it on a schedule. It was a frustrating extra step that confused new makers and added unnecessary complexity to simple automations.
Desktop flows can now be scheduled directly from the Automation Center in Power Automate. You set the recurrence, the target machine or machine group, and the desktop flow to run — all in one interface without a cloud flow in the middle.
For operational teams running dozens of unattended bots on a schedule, this simplifies maintenance and reduces the number of flows to track.
Flowchart View for Complex Flows
Power Automate’s traditional desktop flow designer displays actions as a sequential linear list. For simple flows this is intuitive. For flows with branching logic, parallel sub-flows, and conditional error handling, the linear list becomes hard to follow.
The new Flowchart View renders actions as connected nodes in a diagram, similar to a logic flowchart. Branching paths, sub-flows, and loop structures are visually distinct. Troubleshooting a complex flow is faster because you can see the full execution path at a glance.
Copilot Integration for Flow Editing
Natural language prompting is now integrated into the desktop flow designer. You can describe what a step should do in plain English, and Copilot generates the action configuration or suggests a modification.
For example: “Change the timeout on this file download action to 45 seconds and add a retry on timeout” — and Copilot updates the action settings and wraps it in the correct error handler.
Who benefits most?
For automation developers and Power Platform makers:
- Self-healing dramatically reduces overnight failure rates for unattended flows running against frequently-updated enterprise applications (SAP, Dynamics, legacy web portals).
- The Flowchart View cuts the time spent understanding someone else’s complex flow during handovers or audits.
For IT administrators managing bot infrastructure:
- Native scheduling in the Automation Center simplifies bot run management without requiring cloud flow expertise.
- Self-healing reduces emergency tickets at 3am when an application update breaks an unattended payroll or reporting bot.
For business process owners:
- Bots that previously needed developer attention after every quarterly application update now adapt automatically.
- The reduction in maintenance overhead means automation ROI improves over the life of each flow.
Power Automate Desktop Updates — Summary
| Feature | What it does | Why it matters |
|---|---|---|
| AI Self-Healing | Recovers from UI element failures using computer vision and fuzzy matching | Prevents automation downtime caused by minor application UI changes |
| Native Scheduling | Schedule desktop flows directly in Automation Center without cloud flow wrappers | Reduces complexity for operational bot scheduling |
| Flowchart View | Displays flow actions as connected nodes instead of a linear list | Makes complex branching flows easier to understand and troubleshoot |
| Copilot Integration | Edit and configure flow actions using natural language prompts | Lowers the skill barrier for modifying and maintaining existing flows |
Availability and requirements
| Item | Details |
|---|---|
| Self-healing availability | Organisation premium accounts (Power Automate per-user with attended/unattended RPA) |
| Government cloud support | Not available in GCC, GCC High, DoD, or sovereign clouds currently |
| Native scheduling | Available in Automation Center for all desktop flow users |
| Flowchart View | Available in the desktop flow designer for all plan types |
| Copilot integration | Requires Microsoft 365 Copilot or Power Platform Copilot add-on |
What should you do next?
If you manage desktop flows in your organisation, three practical actions to take this week:
- Enable self-healing on your highest-failure flows first — Open the most maintenance-intensive flows in Power Automate desktop, go to flow settings, and enable the self-healing toggle. Monitor the next run cycle and check the recovery log for any resolved errors.
- Switch to native scheduling for any desktop flows currently triggered by cloud flows — Open the Automation Center, find flows running on a schedule via a cloud flow trigger, and migrate them to native scheduling for cleaner management.
- Try the Flowchart View on a complex flow — Open a flow with branching logic you have not worked with recently. Switch to Flowchart View and see if the structure is easier to review before making changes.
Start small. The self-healing feature is most valuable for production bots running against enterprise applications. Test it in a non-critical environment first before relying on it for overnight payroll or finance reporting automation.
FAQs: Self-Healing Desktop Flows in Power Automate
Does self-healing automatically update the stored element selectors when it recovers?
Not permanently. Self-healing recovers the current run but does not modify the stored element definition in your flow. To permanently fix a broken selector, you should update the flow with the correct new element after self-healing surfaces the mismatch.
Will self-healing work on all types of UI automation actions?
Self-healing is designed for UI and web automation actions that interact with on-screen elements. It does not apply to actions that fail for non-UI reasons — such as file not found errors, network timeouts, or API errors.
What gets logged when self-healing activates?
The Power Automate run history logs the self-healing recovery event, including which element it failed to find originally and which alternative element it used. This gives developers visibility into how many times and where bots are self-correcting.
Is self-healing available for attended and unattended desktop flows?
Self-healing is available for both attended (user-initiated) and unattended (machine-triggered) desktop flows, provided the account has an organisation premium license with RPA capabilities.
How is the Flowchart View different from the existing canvas view?
The existing linear list shows actions in sequential order without visual branching. The Flowchart View renders actions as nodes with connecting lines that show the path of execution, including all branches, loops, and sub-flow calls — making the overall logic visible at a glance.
Does Microsoft publish failure rates or benchmark improvements for self-healing?
Microsoft has referenced implementations reporting up to 75% reduction in RPA maintenance overhead, but these figures depend heavily on the type and frequency of applications being automated. Your results will vary based on how frequently your target applications update their UI.
