So basically we have a new VM running 3 robots and sometimes, the process stops with error of timeout reached. The weird thing is that most of the time the process runs without any problems.
This same processes previously was running on other machine and this error didn’t occur.
Have any of you had this issue and managed to come over it?
Did you try using a retry activity on the activity that is failing…
Or better add a verififcation for the actions performed …so that it can be recovered…it might be some environment issues as well…its very broad to say from this perspective…but anove resolutions might help
@roberto.wengratt
you can try to close the priviously opened tasks and then try to run. or you can put try catch when this happned try to end priviously memry consuming task and run again by providing some retry counter or like that.
The screenshots doesn’t show nothing in particular, only the application opened.
However, looking in the trace, we saw some “Wait Queue Item Timeout reached”.
The problem is that the activity has a Continue on Error as true, and it doesn’t happens on others machines.