- Overview
- Getting started
- Frequently asked questions
Setup
Set up Healing Agent for attended and unattended automations, including activity-level configuration, enabling self-healing in Orchestrator, and bring-your-own-model setup.
Activity-level configuration
Before starting setup procedures, ensure you meet the Healing Agent Prerequisites.
You can also filter Healing Agent features at the activity level, for each individual activity:
- Disabled — Disables Healing Agent.
- Inherit job settings — Inherits all settings from Orchestrator.
- Recommendation only — Healing Agent only provides recommendations, and does not heal the automation.
- Same as app/browser — Inherits the AppCard settings.
If you disable all settings in Orchestrator, modifying settings at the activity level does not affect Healing Agent.
Unattended setup
You must have the role permission of Automation Developer or higher, as well as the following permissions:
Process.EditMediaExecution.ViewMediaExecution.CreateMediaExecution.Delete
Healing Agent is available only for processes executed as jobs.
-
In Studio, open an existing project or create a new one.
a. If you have not done so already, update to version 25.10.2 or later of the UIAutomation.Activities package. b. Optionally, enable the Verify Execution feature, which Healing Agent relies on for input actions. If you have any activities that are not connected to Orchestrator, use the Synchronize Object Repository feature to add all activities to Orchestrator. c. Publish your project.
-
Go to Orchestrator.
a. Select Add process. b. Select Additional settings. c. Enable Healing Agent either at the process level or the job level. You can configure self-healing independently across both the process and job levels.
Note:If you do not activate self-healing, Healing Agent only provides detailed debug information and limited recommendations, and does not take any autonomous actions.
d. Create a new job based on the process you published.
-
Select Run to run your job.
a. Select Job Details. b. Select Healing Agent. c. Select Download the debug file.
Result: The Healing Agent panel displays only if the job involved at least one recommendation or healed action. If the automation project is in your workspace and Studio is connected to the Orchestrator tenant, you can select Open in Studio to open the debug file directly in Studio. Otherwise, load the downloaded file from the Studio Observability panel, as described in Applying Healing Agent suggestions in Studio.
If Healing Agent cannot recover an activity, the Robot logs in Orchestrator show the reason for the failure, for example "Healing agent could not recover the activity. Self-healing is disabled."
Attended setup
You must have the role permission of Automation User or higher, as well as the following permissions:
Process.EditMediaExecution.ViewMediaExecution.CreateMediaExecution.Delete
-
In Studio, open an existing project or create a new one.
a. If you have not done so already, update to version 25.2.1-preview or later of the UIAutomation.Activities package. b. Optionally, enable the Verify Execution feature, which Healing Agent relies on for input actions. If you have any activities that are not connected to Orchestrator, use the Synchronize Object Repository feature to add all activities to Orchestrator.
-
Publish your project.
-
Go to Orchestrator.
a. Select Add process. b. Select Additional settings. c. Create a new process based on the automation you published. d. Enable Healing Agent either at the process level or the job level. You can configure self-healing independently across both the process and job levels. If you do not activate self-healing, Healing Agent only provides detailed debug information and limited recommendations, and does not take any autonomous actions.
-
Run your automation from Assistant. Ensure you select the Report Exception option at runtime.
a. Select Job Details. b. Select Healing Agent. c. Select Download the debug file.
Result: The Healing Agent panel displays only if the job involved at least one recommendation or healed action. To view the debug file, load it from the Studio Observability panel, as described in Applying Healing Agent suggestions in Studio.
Bring-your-own-model (BYOM) setup
To use your own LLM subscriptions, configure them via LLM configurations in the AI Trust Layer:
- In Automation Cloud™, navigate to Admin.
- Select AI Trust Layer, then select the LLM configurations tab.
Note:
The LLM configurations tab requires an entitlement that is granted with your licensing plan. If the tab is not available, your organization's plan does not include it. For the plans that include it, refer to Licensing, and contact your UiPath account team to add the entitlement.
- Select a tenant from the Tenant drop-down, and then select Add configuration.
- In the Add configuration panel, take the following steps:
a. Select Healing Agent from the Product drop-down.
b. Select Workflow Recovery from the Feature drop-down.
c. Select Replace UiPath LLM subscription.
d. From the Folder drop-down, select the folder in which you want to store your LLM connection.
Note:e. For your Replaceable LLM, select a connector from the Connector drop-down, and then select Add connection from the Connection drop-down. f. A new tab opens. Populate the fields required to connect UiPath to your selected connector, then select Test in the Add configuration panel. g. Select Save.
Avoid storing your LLM connection in a folder that is shared with other users. Credentials saved in shared folders can be accessed by anyone with access to the folders and may expose your organization’s API keys or model data.
Result: Healing Agent uses your configured LLM subscription for workflow recovery.
For more information, refer to Configuring LLMs.
Applying Healing Agent suggestions in Studio
Healing Agent runs against published processes. When a run produces recommendations or healed actions, you can load that data into Studio and apply the suggested selector changes directly to your activities.
Starting with Studio 2026.10, Healing Agent data is available in the Studio Observability panel. In Studio 2025.10, this data was available in the Autopilot panel.
Prerequisites
- The project is published to Orchestrator and has at least one run with a Healing Agent recommendation or healed action.
- To analyze the most recent healing data directly, log in to Studio and Orchestrator with the account that published and ran the project.
- To load healing data from a file, download the debug file from Orchestrator first. Go to Jobs, select Job Details, select Healing Agent, then select Download. The Healing Agent panel appears only if the job involved at least one recommendation or healed action.
To review and apply Healing Agent suggestions:
-
In Studio, open the project for which you want to review suggestions.
-
On the Studio right rail, select the Observability icon.
-
In the Runs section header, open the options menu, then choose the option that matches your case:
a. If Studio and Orchestrator are connected to the same tenant where the jobs ran, choose Analyze most recent healing data.
b. If they are not, choose Load Healing Agent data from file, then select the debug file you downloaded from Orchestrator.
-
In the Runtime healing data view, check Process details for the process name, run date, and how many errors were healed.
-
Under Affected activities, expand an activity to review its suggestion. Details explains why the original target failed, and Suggestion describes the proposed change. The Target and Anchor tabs show the current definition against the generated one.
-
Select Apply to update the activity with the new target.
Result: The activity uses the generated target definition. Repeat for each activity listed under Affected activities.