I am developing a workflow using StudioX 2022.4.6 on Windows 10.
I am debugging a workflow that sequentially reads Excel files placed in a specified folder and performs web scraping.
The execution always stops around the 90th or 100th row of the first Excel file.
The stopping point is different each time (the reason is a UI identification error).
Sometimes it stops at the second activity after loading the web page.
Is it possible that a memory leak is occurring because the UiPath version is old?
However, as I initially pointed out, it’s unlikely the web server is congested nightly, and the problem occurs even on the second activity after a page reload, not just the first. Therefore, I don’t think your approach is appropriate.
It would be better to find another approach.
To understand better when the automation fails dont stop and open the ui explorer or keep it open and then indicate the application and see if any attributes are varying
As per error its failing in attach itself ..so check the same
The version StudioX 2022.4.6 is not supported, and as I remember, even in 2023.4.x Studio had some memory leaks for some specific use cases.
Try upgrading StudioX to a supported version from 2023.10.15/2024.10.21/2025.10.11 (upgrade the UiPath.Excel.Activities, UiPath.System.Acticities and UiPath.UIAutomation.Activities packages also) and retry the automation.
