Hi all. My bot published locally in my pc suddenly has issue. Running in UiPath Assistsnt, the first part of the bot is working fine but when it reaches a specific page, the bot stopped working as it is unable to detect and click on an element. This bot has been working for the past 2 years so is it pretty strange that it stopped working suddenly.
Any idea on how to get it working again?
There could be changes in the target application. Re indicate the ui element and republish the package.
Hi @marct
I am able to understand that your code is dropping in mid
You can try below steps:
Go through the ui element selectors where it is dropping , work on the page loading issue here you can use check app state check browser extension as well !
If not working try reinstalling browser extension.
Hope it works !
If it works mark as solution solved
chnages in target application can cause it..check the selector specifically where it is failing
also sometimes te previous step might be successful but the landing page might be wrong or so..check accordingly
cheers
Hi @marct
Yes, this is common. The bot didn’t “break suddenly” — the UI changed or the runtime environment did.
Regards,
Gokul
Changes in the target application may cause this issue. Please check the selector carefully at the step where it is failing.
Also, sometimes the previous step may succeed, but the application might land on an unexpected page or state. Verify the application state before proceeding to the next step.
@ashokkarale @vhvinodsai @Anil_G @Gokul001 @MohammedShabbir
The script is working fine in Studio and the said element is showing validated.
I have republish the script but the issue persist.
Please ensure below checks:
Do you hvae the screenshot while it is failing?or when it fails does the bot stay on the correct page?
Is the error still about selector? If so can you show the selector being used here
Cheers
Hi @marct
• The target app/web page UI may have changed (HTML update, new iframe, dynamic IDs).
• Try indicating the element again and compare the selector with the old one.
• Check if browser or application was auto-updated recently.
• Make sure screen resolution, display scaling, and DPI settings haven’t changed.
• Run in debug mode and use Highlight to see if UiPath can still find the element.
• Try switching click method (Simulate / SendWindowMessages / Hardware).
• Clear browser cache or restart the app/PC.
The bot fails and stay on the correct page.
This is the error when running UiPath Assistant.
UI element is able to be detected on Studio
Could not find the UI element corresponding to this selector:
at UiPath.Core.Activities.ScopeActivity.OnFaulted(NativeActivityFaultContext faultContext, Exception propagatedException, ActivityInstance propagatedFrom)
at System.Activities.Runtime.FaultCallbackWrapper.Invoke(NativeActivityFaultContext faultContext, Exception propagatedException, ActivityInstance propagatedFrom)
at System.Activities.Runtime.FaultCallbackWrapper.FaultWorkItem.Execute(ActivityExecutor executor, BookmarkManager bookmarkManager)
looks like its failing on attach browser or use app browser only..you might need to check if the title is changing or use wild cards in it to make it dynamic
cheers
@vhvinodsai @ashokkarale @Anil_G @Gokul001 @MohammedShabbir @Balachandrasekhar_C @Monali_Vekariya
Will deleting the C:\Users<Username>.nuget\packages\UiPath folder help?
Hi @marct
Yes, it can help. Deleting the C:\Users<Username>.nuget\packages\UiPath folder is safe and often fixes issues caused by corrupted or mismatched packages across different Studio versions. UiPath will automatically re-download the required packages the next time you open the project or restore dependencies. This is a common troubleshooting step for package-related errors.
The issue is not related to package but the window changes or title changes
please show the selector of your window here or refine it yourself
delete these packages might not help in this case
cheers
Hi,
Since the automation has been working for the past 2 years and now fails only on a specific page, this is most likely not a logic issue, but an environment or UI change.
I would suggest checking the following:
Application / Web UI changes
Even minor UI changes (dynamic attributes, new iframe, shadow DOM, etc.) can break selectors. Open the workflow in Studio and re-indicate the element where the failure occurs. Prefer stable attributes or anchor-based selectors.
Screen resolution or display scaling
If the bot is run via UiPath Assistant, any recent change in screen resolution or scaling (125%, 150%) can affect element detection. Ensure display scaling is set to 100% and avoid image-based or coordinate-based clicks.
Browser or application updates
Silent browser or application updates can impact selectors and UI frameworks. Make sure the UiPath browser extension is updated and compatible with the current browser version.
UiPath Studio / Robot version or corrupted packages
If UiPath was recently upgraded, local NuGet packages may be corrupted or mismatched. Close Studio and Assistant, delete the following folder, and let Studio restore packages:
C:\Users\<Username>\.nuget\packages\UiPath
Timing and page load readiness
Add proper waits such as Wait for Ready = Complete, Element Exists, or validate that the page is fully loaded before performing the click.
After re-validating the selector and republishing the process, the issue should be resolved in most cases.
Hope this helps.