Activity timeout never reached

Help
1

Hello Community,

Sometimes I encounter a problem where robot “pauses” on a random activity when an unexpected application error window pops up,

Robot is doing various click, type into, get text activites, and when a random application error window pops up the robot is waiting forever. It doesn’t stop and throws no error.

The workflow is prepared to catch any unknown error and restart application due to timeout.

When I manually close the popup, the robot resumes without error and continues.

Many activities has WAIT FOR READY property set to COMPLETE, Does it override the default activity timeout?

2

Hi @Sparrow,
You can test it by adding Delay activity for couple seconds before other let say ‘problematic’ activities. You will see if this will help.

2 Likes
3

Using Delay activity between other activities is a good approach?

4

Not ideal but for test purposes why not to try?

5

Okay:+1::slightly_smiling_face:

1 Like
6

Thanks for the tip, but it didn’t worked. The pop window is totally random and seldom. I have 50+ ui interactions within the app windows, and there is no control when it appears. It looks like warning popup window disables all the controls within the application, and re-enables them after “OK” is clicked. This causes the robot to pause.

Is there any way to execute the timeout of given activity and throw an error? This would allow application restart and recovery.

7

Could you try run the whole thing in a parallel? One route would be to constantly monitor for that pop up and if it appears click OK?

3 Likes
8

Hi @Sparrow,

@TimK is correct.

If you want to continue processing, you can set an ‘Element-Exists’ within a ‘Do-While’ loop in ‘Parallel’ to your current existing process, and then depending on what you want to do when the pop-up appears, you can go forth and:

  1. Close the applications and let your re-try mechanism kick in.
  2. Click ‘OK’ and let it resume the execution.

What I am also interested in is, how many times do you expect this erroneous pop-up in a single end-to-end flow execution? (as this may affect the kind of solution/workaround you’ll need to build for this behavior)

2 Likes
9

Thanks. This seems very ok. Robot is processing a few hundreds of items per day everyday for 10 hours. The pop appears few times a week. After closing the popup everything is fine for hours. Intercepting and servicing this dialog box once should be enough.

10

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.