There might be several reasons for this issue.
First of all, please check all your Global variables are made null or empty for each loop unless you need previous values on them. because this occupies temporary buffer memory in the system which is going to cause slow in your execution.
Second, You have to check in your code how many waits you have used. also check you have proper sync activity with application. also please check nested loops in your WF. also see if you have used any property exists activity which will wait more than a normal time… these activities will show impact on performance. also run step by step and see out put values and check what might be causing issue to stop. if you suspect any step not able to find and failing the execution, then use eliment exists property and report output value in a message box and see each loop your WF is property detecting the element or not. some times element will take more time to load… that might be sync issue. some times element will change property in the back end. So, do some research… and you will find the solution. Hope my inputs are useful.
We’re facing the same issue as well. I have a process where few workflow looping around. It works perfectly fine for 2 hours. Right exactly after 2 hours the robot fail to find the selectors which it has successfully able to find it before.
So is there anything I have to check with my VDE? Please advice.
Neru, please try to increase VDE ram in the VM ware server. also make sure you have a cleaning script get activated for every 100 iterations of processes. Make sure you have a iteration counter and every 100 iteration bot should activate cleaning script.
Cleaning script should contain as follows:
Clear all temporary files in the temp folder of your VM.
Clear browser cache if you are using any browser in your WF.
Close all MS office applications if you are using any office tools like documents, excel… etc… because they will create temporary files which will use some memory space of the machine.
Please modify your design to accommodate this cleaning script.
How ever, as per your inputs, your bot is not detecting selector after some time…
This might be … the case of Dot.Net version. Some times Dot.Net 4.5 is not available or corrupted then it will not allow UiPath to detect object properties by selectors. if it is happening very frequently … then i recommend to remove your Dot.Net frame work in your VDE and re install freshly.
that will definitely fix your issue… else change VDE.