Overview
I have an activity like: "Do something on msedge.exe when edge title contains ‘.xlsx’"①
I use 2 activities:
1/ check exist edge - title ‘.xlsx’
2/ specify browser scope when 1/ exist
And repeat ① for a list of data. Each row call ① one time. (I have ~100 rows)
Everything was fine until 2025/03/18.
But on 2025/03/18, after a period of about 1 hour (specifically: 01h03m - iteration row=25) an exception was thrown.
UiPath.Core.SelectorNotFoundException
System.Runtime.InteropServices.COMException
=> Up to now, the above phenomenon has happened 3 times.
All 3 times happened at the same time (after a period of about 1 hour)
About robot process, nothing has changes.
I wonder if there has been a recent version change of UiPath?
Detail of Process 1 and 2
1/ UiPath.Core.Activities.UiElementExist
Detail of Process 1 and 2
1/ UiPath.Core.Activities.UiElementExist
wnd app=‘msedge.exe’ cls=‘Chrome_WidgetWin_1’ title=‘.xlsx ’
2/ UiPath.Core.Activities.BrowserScope
html app=‘msedge.exe’ title='.xlsx’
UiPath.Core.SelectorNotFoundException html app='msedge.exe' title='*.xlsx*'
System.Runtime.InteropServices.COMException html app='msedge.exe' title='*.xlsx*'
While you’re using UiPath Studio 2022.4.9, there might have been updates to related packages (e.g., UiPath.Core.Activities or browser-related extensions). Check the following:
Open Manage Packages in UiPath Studio.
Verify if there are updates available for activities like UiPath.Core.Activities.
Confirm that the browser extension for Microsoft Edge is up to date. Browser updates can sometimes cause changes in selectors.
2. Selector Dynamics
A SelectorNotFoundException often indicates that the UI element cannot be identified. Since this occurs after an hour, it may be due to dynamic changes in the browser window. Try the following:
Refine the Selector: Use wildcard characters (*) or variables to make the selector more adaptable. For example:
<title>*xlsx*</title>
Validate the Selector: Open the UI Explorer in UiPath and validate the selector during runtime to ensure it’s still identifying the element.
Delay Before Checking: Introduce a slight delay before the UiElementExists check to allow the browser to stabilize.
3. Edge Browser Behavior
Browser caching, memory usage, or a session timeout could impact your workflow. To mitigate:
Use the Close Tab activity after each iteration to free up system resources.
Clear the browser cache periodically during runtime, if possible.
4. Exception Timing Pattern
The consistent timing (around 1 hour and 3 minutes) suggests a possible session timeout or memory/resource exhaustion. To address this:
Use the Kill Process activity to terminate msedge.exe at intervals, then relaunch it before continuing.
Monitor system resources (RAM, CPU) during execution to check if the robot process or browser is consuming excessive resources.
5. Logs and Debugging
Enable verbose logging in UiPath to capture detailed information about what occurs just before the exception.
Analyze the logs for patterns, such as memory leaks, failed attempts to find elements, or application crashes.
I’m wondering if the abnormal robot behavior is related to the updated version of the Edge extension?..
I see there is an update version on 13/3/2025.
Is it possible that UiPathRobot lost connection with WebAutomation?
Because the errors occur every time after 1 hour of startup.
