Unknown Error in Retry Scope

Help Studio
, , ,
1

I have a robot that runs continuously every 15 minutes. While it operates without any issues during a single run, I occasionally encounter some unknown errors when it runs continuously. After closing UiPath and restarting the robot, the errors do not occur again.

Two examples of these errors are as follows.

My questions are:

  1. Can anyone help explain why this issue is happening?
  2. What factors might be contributing to these two errors?

image
image400×215 14.8 KB

image
image569×319 15.1 KB

2

Hey @boxli this error is coming because the activity inside the Retry scope like Click or type into or any ui activity is trying to look for the target and it could not find the element where it need to be perform thats why it throw error.please make sure your selector is fine tune. use attach window or use application/browser if the window is changed the use the click or any other activity and fine tune the selector.

cheers

3

@boxli

  1. That generally comes when memory is out ..occurs in long run..better to clear the unused variables or data intermittently
  2. I guess there is a find element or so you have given in condition of retry which might be failing

Cheers

4

Thanks for the insight! Just to clarify, I don’t see any errors during single runs, only when it runs continuously for a long time. This makes me wonder if there’s something specific about the prolonged execution that triggers these errors. Any thoughts on why that might happen?

Cheers!

5

Thanks for the suggestion! How can I clear the variables to prevent issues during a long run?

Or are there other activities to prevent long run error? I’m using a do-while loop to have the robot run every 15 minutes.

Cheers!

6

@boxli

assign the variables to nothing after use so that memory is freed up

if you are keeping any window or so open try to close and reopen instead

any temporary files created can be deleted

and this is one of the cause …so you might need to check the cpu performance when this occurs if its at peak then we might need to clear few temp files

cheers