UiPath Healing Agent Community Public Preview

[gheorghestan]

Overview

We’re excited to announce the community public preview of Healing Agent. This capability includes a set of AI-powered experiences across UiPath Robots, Orchestrator, and Studio to reduce automation downtime and enhance efficiency. It provides:

• Intelligent self-healing for UI-based automation: whenever there is a change in the application interface or the automation is obstructed by UI interference, Healing Agent repairs the issue to allow the automation to continue uninterruptedly
• Actionable recommendations: Healing Agent intelligently analyzes the application interfaces and provides targeted suggestions to minimize time spent on troubleshooting or debugging, enabling quick resolution of issues and allowing the automation to be put back into production as soon as possible.

Demo

UiPath Healing Agent - full demo

What are the use-cases where UiPath Healing Agent helps?

How does Healing Agent complement Unified Target?

Unified Target is a feature in UiPath that provides a more advanced, flexible, and unified approach for targeting and interacting with user interface (UI) elements during automation. It simplifies how robots identify and interact with UI components across different applications and platforms, enhancing the resilience and accuracy of automation. Instead of relying solely on strict selectors, it combines multiple methods such as fuzzy selectors & anchors, computer vision, and semantic targeting to ensure better element identification. If a UI element changes (e.g., layout, position, or attributes), the unified target can fall back on alternate methods (like image recognition or semantic labels) to maintain automation continuity, minimizing failures. Works across various platforms and technologies (e.g., web, desktop, legacy systems), making it easier for developers to build automations that adapt to different environments.

The execution happens before activities time out.

Healing Agent complements UiPath Unified Target. It is designed to increase the automation resilience if a unified target fails to find the configured target.

Healing Agent gets involved only if it is enabled at the process/job level, and only after activity timeout and the process is about to fail.

What are the supported project types?

Healing Agents support Windows and Cross-platform project types.

Does it work for existing or new projects?

Some recovery strategies can be applied to existing projects, while others are designed specifically for new projects. The latter requires additional information to be collected during the design phase, as UIAutomation activities are configured.

Note: The UIAutomation.Activities package must be version 24.12.3-preview or higher, and the Robot version must be greater than 24.10.

Does it support both UIAutomation Modern or Classic activities?

Healing Agents support UIAutomation Modern activities only.

What types of applications/environments are supported?

Both desktop and web applications.

Also, Healing Agent can recover automations designed to run on remote environments. E.g. Citrix

Limitations

• Only Windows and Crossplatform projects are supported. Legacy projects are not.
• The Healing Agent can close intruding popups/dialogs only if the UIAutomation activities are using the VerifyExecution feature. This is the only way the agent can determine whether the popup window is supposed to be there or not.
• Targets based on Computer Vision only, cannot be recovered as of now.
• Classic UIAutomation activities are not supported
• Healing Agent cannot detect dialogs or interfering external applications if the automation is executing with applications exposed via RDP, Citrix or VMware
• Healing Agent cannot detect dialogs or interfering external applications if the automation is executing with applications exposed via RDP, Citrix or VMware
• Healing Agent cannot detect Alerts/Prompts if the automation executing happens on server-less robots.

How it works

Unattended Scenario

Attended Scenario

To learn more about how Healing Agent works in UiPath, take a look at this page:

Key features

Here is a list of the functionalities included in the public preview

Unattended experience

• Automation Self Healing
• Automation Fix Recommendations
• Dedicated Healing Agent Panels

Orchestrator Experience

• Feature Configuration at Process and Job Level
• Dedicated Healing agent Panel on Job Details
• Download Debug File/Open Studio feature

Studio Experience

• Dedicated Autopilot panel to explore Debugging Information
• Apply Automation Fix Recommendations

Attended experience

• Runtime Fix Recommendations
• Runtime Manual Fix
• Exception Reporting

Get started - Configuration

The Healing Agent includes multiple sub-features (/experiences) as described above, some of which can be tested independently.

You have the option to enable all configurations to test the entire feature, or you can choose to focus on testing specific parts.

Below, you can find the steps of the major testing scenarios you can explore during the public preview.

The best testing scenarios are existing UiPath projects that fail(ed) often due to UIAutomation issues.

Pre-requisites

• Orchestrator: https://cloud.uipath.com/. (Features are supported only in the cloud, on-premises configuration is currently unavailable).
• Studio: latest Community version (You can download it from here: UiPath)
• Robot: 24.10 or later
• UIAutomation.Activities Package: 24.12.3-preview

Unattended Experience

1. Orchestrator

• Connected to https://cloud.uipath.com/{tenant}
• Role permission needed: Automation Developer (or higher)
• If the out of the box roles are not used ( or custom ones are), then these permissions are mandatory:
  • Process.Edit - to be able to alter the A4R settings as well
  • MediaExecution.View - to be able to view the info and download the files
  • MediaExecution.Create - to be able to add the debug files (this applies to the Robot role)
  • MediaExecution.Delete - to be able to delete the recommendation; this operation is also audited

2. Machine

• Connected to https://cloud.uipath.com/{tenant}/folder

3. Studio

• Either use an existing Windows project or create a new one - only Windows and Crossplatform projects are supported

• In certain cases, the effectiveness of Healing Agent relies on the Verify Execution feature for input actions (like Type Into, Click, etc.). We recommend utilizing Verify Execution in your processes used for testing to more thoroughly evaluate the healing mechanism.

(Check here the Verify Execution property)

For the Unattended running, any Studio version 21.10 or later will work.

For the Studio experience (where you can view and apply the recommendations within Studio) a Studio update is required. Please refer to the instructions provided below in section Studio Developer Experience.

1. Update to 24.12.3-preview UIAutomation.Activities activities package.

   For existing projects: check the process for errors & solve them.

   If Studio >= 24.10, Object Repository is enforced. If you have activities that are not connected to OR, use the Sync Object Repo feature to add all automatically to OR.

   

2. Optionally, enable the VerifyExecution feature.

3. Publish Process.

4. In Orchestrator:

5. Enable Healing Agent either at the process level, or at the Job level

• Process level settings
  
  • :Self-healing can be configured independently.
  • If self-healing is not activated, no autonomous actions will be taken. In this case, Healing Agent will only provide detailed debug information, but limited recommendations.
• Job level settings
  
• Create a new Job based on the Process published above

Healing Agent is currently available only for Processes executed as Jobs, not for other types of Jobs like Triggers and Test cases)

• • Run Job
  • Check Job Results: Go to Job details → Healing Agent panel.
    • The Healing Agent panel will only appear if there has been at least one recommendation or healed action; otherwise, the panel will remain hidden.

For the “Download debug file” and open in Studio experience, follow the steps below.

Studio Developer Experience

Prerequisites

• Download the latest Studio Community version.

• You can find it here: Resource Center - Automation Cloud

  

1. In Orchestrator, navigate to the job and download the debug file

   

   • Once you tap on Download, a Notification when the report is generated should be available in Orchestrator, taking you to My reports. if it’s not, please make sure to subscribe to Export alerts. (Automation Cloud Profile → Preferences → Notifications → Orchestrator → Exports)

   • If the automation project is already in your workspace and your Studio is connected to the Orchestrator tenant, you can use the ‘Open in Studio’ feature to directly open the debug file in Studio, correlated with the process.

2. Studio:

   • Open the Autopilot panel
   • Import debug file
   • Select the previously downloaded file
     
     
   • Explore/Apply Recommendations

Attended Experience

Configuration is the same as in the Unattended experience described above up to and including step 5.

For the automation user: Role Permission - Automation User (or higher).

• In Orchestrator (in the desired folder)

  • Create a new Process based on the automation published
  • Enable the Healing Agent

• Self-healing can be configured independently.

If self-healing is not activated, no autonomous actions will be taken. In this case, Healing agent will only provide detailed debug information, but limited recommendations.

1. Run automation from Assistant.
2. If the user selects the “Report Exception” option at runtime, then, in the Orchestrator, the “Autopilot” panel should be available in the Job details as in the Unattended case.

[ruchirmahajan]

The most awaited feature of the decade

[ashokkarale]

Thank you for sharing a detailed guide @gheorghestan! Lets try the power of AI in every product

[Akash_Javalekar1 (Akash Javalekar)]

Wow finally wait is over Can’t wait try this feature

[ShivpujanK (Shivpujan Kumar)]

It’s great to see this coming.

[loginerror (Maciej Kuźmicz)]

We are super excited about this feature. Please post any feedback that you have about it.

We are curious what you think!

[sharazkm32 (Sharaz K M)]

It took me around 5 minutes to update the package. Is this expected?

[Akash_Javalekar1 (Akash Javalekar)]

@sharazkm32 No it wouldn’t take much time I did tried check your studio version once

[ashokkarale]

@sharazkm32,

It depends on your machine hardware and internet speed.

[kashif.ansari417]

I don’t see the option to enable healing agent at process/job level. My orchestrator version is 2024.10.0-s156.3316. Is this feature is not there yet for me and still rolling out? I make sure to use UiAutomation activities with version 24.12.3-preview.

[kashif.ansari417]

Never mind. It was not showing on a pro trail license but available on the community one.

[kashif.ansari417]

Tried this awesome feature and works great.

[Jobin_Joy]

I explored the ‘Auto Healing Agent’ feature and developed a simple POC that works flawlessly

[rkelchuri (ER.Krishna)]

Do you have documentation on the same ? please share here if possible.

[gheorghestan]

ClickUp

[Sumit_Ahlawat]

How we can notify the admin if any selector fails and fixed by healing agent so that developer can apply the recommendations ?