Submission type
Healing Agent Challenge
Name
Anikesh Srivastav
Industry category in which use case would best fit in (Select up to 2 industries)
Information technology and services
Complexity level
Beginner
Summary (abstract)
As part of the “Fix It with Healing Agent” challenge in UiPath, I built a test automation workflow simulating the creation of new client accounts in an enterprise Salesforce environment.
The bot performs the following steps:
- Logs into Salesforce using secure credentials
- Navigates to the Accounts tab
- Clicks the New button to initiate account creation
- Fills out the account form with dynamic data
- Saves the account and repeats the process
- Logs out upon completion
While the workflow itself is straightforward, it is highly sensitive to UI changes, such as renamed form labels or reordered sections, common in evolving platforms like Salesforce. This exposed a critical limitation in conventional automation: fragile selectors that break with minor UI modifications
Detailed problem statement
In dynamic enterprise platforms like Salesforce, frequent UI updates, such as field renaming, layout changes, or added components, break traditional RPA selectors.
This leads to:
- Automation failures in production
- Time-consuming manual debugging
- Increased maintenance effort and costs
In my implementation, the bot failed when:
- The “Details” section label was renamed to “Description”.
These seemingly minor changes caused selector mismatches, breaking the workflow and halting account creation automation.
Detailed solution
To tackle this, I enabled UiPath’s Healing Agent.
Key actions and learnings:
-
Healing Agent automatically detected UI changes and matched updated elements (e.g., renamed labels) with a high degree of accuracy.
-
HA recovers selectors per transaction, i.e. the HA will kick in for every transaction even if it has already recovered the selectors in one transaction.
-
Even if selectors are linked to Object Repo, and HA fixes one of the selectors, it will still kick in for other transactions.
-
To persist changes across runs, I applied the generated debug file and upgraded the project dependencies to the latest version.
This solution restored automation stability and made the bot resilient to minor UI shifts, without re-recording or updating selectors manually.
Expected impact of this automation
The use of Healing Agent delivered measurable benefits:
Zero Downtime: Automation continued running even after UI changes
Debug Time Saved: Avoided hours of manual RCA and selector fixing
Lower Maintenance Overhead: Reduced bot rework and regression effort
Increased Bot Intelligence: Improved resilience using AI-powered healing
Better ROI: Reduced cost per bot run and faster deployment in dynamic environments
Faster Recovery: Faster turnaround when changes occur in production
UiPath products used (select up to 4 items)
UiPath Studio
UiPath Orchestrator
UiPath Healing Agent
Automation Applications
Salesforce
Integration with external technologies
N/A
