Submission type
Healing Agent Challenge
Name
Prashant Kumar
Industry category in which use case would best fit in (Select up to 2 industries)
Logistic
Manufacturing
Complexity level
Advanced
Summary (abstract)
I automated the invoice reporting process on our company’s manufacturing portal using UiPath. The bot logs in, downloads invoice report Excel files, creates new reports using templates, processes data, and sends summary emails. But when the portal’s UI changed, selectors broke, and the bot stopped working. Instead of fixing selectors manually each time, I used UiPath’s Healing Agent, which fixed broken selectors automatically while the bot was running. This made the automation more stable and saved lots of manual effort.
Detailed problem statement
The invoice reporting bot used to work fine until the manufacturing portal changed its UI. Buttons for login, invoice reporting, exporting, and uploading moved or got renamed. This caused the selectors inside the workflow to break, and the bot failed to find those elements. We had to stop automation, find and fix broken selectors manually, and test again. This process took too much time and delayed reports. We wanted to make automation more reliable and reduce maintenance effort.
Detailed solution
I enabled UiPath’s Healing Agent in the workflow. The bot’s main tasks include going to the company manufacturing portal, logging in, selecting invoice reporting, searching and downloading Excel attachments to a shared folder. Then it creates a new invoice report using a template, copies data from the downloaded file into the new report, and adds columns, formulas, and pivot tables to process the data. After that, it goes back to the portal, exports the previous report, merges data from that report to complete the new one, and saves the final report in the shared folder. Finally, the bot sends a summary email with the report status.
To test Healing Agent, I deliberately broke selectors by changing button names and menu structures. When the bot ran, Healing Agent detected the broken selectors and fixed them automatically. The bot kept running smoothly without errors and completed all the steps perfectly. (As i mentioned in To-Be diagram)
Expected impact of this automation
The biggest benefit is the huge time saved from not having to fix selectors manually every time the portal UI changes. This means less downtime for the automation and faster report generation without waiting for manual fixes. It also gives us more confidence that the bot will keep working even if the portal changes again. Overall, it reduces maintenance effort and improves the reliability of the process.
– Saves many hours of manual fixes
– Reduces automation downtime
– Speeds up report updates
– Improves confidence in Bot stability
I have attached my output images where bot automatically apply Healing to the selectors.
UiPath products used (select up to 4 items)
UiPath Studio
UiPath Healing Agent
Automation Applications
Invoice MES
Integration with external technologies
Microsoft 365
TO-BE workflow/architecture diagram (file size up to 4 MB)
Other resources
NA