I am running a process, which selects into an attach browser and does an activity with various clicks. This process needs to run for varying amounts of time. From the start until a certain point it finds all the selectors with no issues and goes into each if section (with another attach browser) and finds the selector there with no issue, but after the robot has run for over an hour, i get to a point where it goes into the same if section it always has done, but now i get the error saying:
"cannot find ui element corresponding to this selector: "
This has happened 3 times after it has run for around 1.5 hours. Doesnāt say which selector, but looking at my log messages it can only be the same attach window it previously hadnāt failed on (as the log messages end before and after this). However, my selector has a long number in it, to me, random, but must have some sense behind it, and Iām thinking because this process has run for such a long time, this number may have changed in the process?
This has now happened again, after I added wildcards to the selector. Same issue where it has reached this part of the process 5/6 times, but has now failed on the last attempt mid run, with no indication of what the selector is
Once the process fails, does it stop completely or do you have clean up code after it?
If you make it stop right then and there, you could use UiExplorer to see what is the proper selector for the window itās trying to find and compare to what is in the workflow. Something has to be changed OR thereās an unfound instability.
There is clean up code after it, and I have been able to see exactly where the selector has now changed.
However, I have just run again, all my selectors have wildcards now, but the same thing has happened! After about 1.5s worth of work the robot has stopped; I then went to try and stop the execution, but uipath was not responding, to the point where I could only end it using task manager on my PC.
could this be something to do with RAM space on the PC or soemthing i have in the code telling it to stop at this point every time??
I have version 2016.2.6442
Any help would be great, as Iām not sure what else could be stopping it at this point every single time
Did you check what was the memory usage before you killed the process?
It might be that itās allocating indefinitely (either by an error in workflow or memory leak somewhere).
Looking into my logs, it excecuted the last selector, and then the process is meant to throw to the catch and another log message (using an append log method) is meant to come up, which it didnt. So either the throw failed (and im not sure how), or the append log. This process is a loop and should be running all day, but from what my colleague and I have seen, theres no clear reason why it would have failed here, when its worked for an hour and these are just uipath processes.
Looking at the file size of the workflow it stops in its over 5GB!
Sophie - hello.
I have had a similar issue. Iām working with an access database screen objects return different selectors ā¦ I mean ā¦ the same screen object returns different selectors !!!
I am extracting data from an object and sometimes IDX=ā2ā and sometimes IDX=ā3ā ???
It has taken me three days to pinpoint this behaviour ā¦ now I am know what the issue is ā¦ I can combat the problem.
I donāt want anyone else to have the same pain as me
I would be interested to hear of anyone else having a similar problem
Hugh
PS - I have called this behaviour Wandering Selectors
secondly, yes, I also found this not too long ago! but my issue wasnāt actually the selectors in the end, it was the application itself crashing after running for over 2 hours, with masses of automation thrown at it!
I know this may be an old post but I am facing the same issue and it seems like āidxā is the culprit. It changes ārandomlyā as far as I can tell. My āattach windowā selectors and āsend hotkeyeā selectors are all throwing error that they can not find a matching selector.
Ajay_Mishra
ashokkarale
Abhi_Nande
Asantewaa_Mantey
mikko1
E.Y.9
Phenyo