Timeout Reached on remote desktop - but activity is successful

Help Activities
, ,
1

I have seen many topics on the “Timeout reached” error, but none where the activity is successful. In my case, the activity is successful, but I still receive the error after the activity has executed.

UiPath Assistant was installed in Attended mode, and connected as unattended robot by machine key, set up as a standard machine in Orchestrator
Using remote desktop, I am logged in to remote desktop, and closed the RDP window (without logging out)
I am using Use Browser activities with Chromium API
The error occurs on Click activities
If I click Ignore on the error during debugging, I can continue through the entire process

08/14/2023 15:23:06 Click Job Branch dropdown: Timeout reached.

I understand the above setup is not recommended (recommended to install in Service Mode, log out of RDP session, etc.) but in my case it is working well enough to find the selectors and execute the clicks.

Why would this error occur if the click is successful? Are there any changes I could make in the activities / properties to avoid this error?

Currently I am using a global error handler, where if the errorInfo.Exception.Message = “Timeout reached.” then Ignore, else Retry.

2

@KevinE

Try changing chromium api to simulate…looks like click is happening but the response is not received or the ui is changing after that

And yes first of all as you mentioend service mode and aignout are important

Also first try checking the interqctive option in click

Cheers

3

Hi @KevinE ,
activity fail after 30s, I think in WF have click activity fail,
you can check default
wait page load, check element exist before click
edit delay before click, and edit attribute, edit selector
regards,
LNV

4

Hi, sometimes, after a successful click, the UI might undergo updates or changes that result in a delay before the subsequent activities can be performed. This could lead to timeouts, even if the initial click was successful. To address this, consider adding a small delay (using the “Delay” activity) after the successful click before proceeding with the subsequent actions.

5

I should have also mentioned I can’t use simulate because I need to click offset from the target by 40px, and get a warning that offset is not supported with simulate. I tried but it didn’t click with the correct offset.

Yes the UI does change after most of the clicks, there will be a popup or overlay, etc. after the click.

I tried reinstalling with service mode the other day, but that caused other issues with logging in to NT AUTHORITY/LOCAL SERVICE, so I reverted back. I’d rather use the global handler instead of reinstall in service mode for now, but wondering if there is a better explanation / solution for the error.

6

I believe those all deal with an activity failing to click. My activity is not failing to click. Mine is clicking successfully, but still throwing an error. If you have any specific suggestion if you have dealt with this specific issue.

Activity is not failing after 30s timeout. The click happens successfully, then the error message comes after about 5 seconds.

7

Subsequent activities can be performed immediately. There is never any problem with the subsequent activity, the only problem is the error in the current click activity, which comes up even though the click is successful.

I have tried your suggestion though and added a delay after click, I still get the timeout error.

8

@KevinE

  1. Try to include a delay before
  2. Use wait for load complete
  3. Already as you are clicking with hardware events then offset is something you would be using

cheers

9

What’s next activity?
You can check time delay before of it
Cheer,
LNV

10

I tried 2 minute delay before and after. The activity waits 2 minutes before clicking, then clicks, then gives the timeout error after about 5 seconds. So it seems like the timeout error comes before the 2 minute “delay after”.

I tried all the different “wait for load” options, no change

I am using chromium API (can’t use hardware because I am running on remote server while the RDP window is closed)

I should add - when I run the same process while the RDP window is open, I do not get the timeout error. I’m wondering if the chromium API has some built in action to wait for a response from the webpage even after sending the click, and maybe the response doesn’t come if the RDP window is closed. But there doesn’t seem to be any option to control that. I was also wondering about the “WebDriver mode” option in Use Browser container.

Anyways, I appreciate the replies, I guess I will just stick with my global handler solution for now, and try to set up the unattended bot correctly later on.

11

Next activity is click. In total there are 10 clicks and one send keyboard shortcut.

Checking the time of delay doesn’t seem to be related to the timeout error. Think if I have activities Click1 and Click2. The Click1 activity is executing properly, it is clicking the webpage. But I am getting the timeout error from the Click1 activity, after it successfully clicks. I am not getting the error from the next activity, I am getting it from the first activity.

12

@KevinE

Even chromium api does not support offset right…and is offset needed because you need to click else where?

Is that element not identified? Did you checkt he ui explorer visual tree to check if you could get that element?

If you can make it proper unattended then it would be good…else you global exception handler is also a good move…apart from
That can try using continue on error peroperty on the click activity in combination with check app state…this way the click would be verified also it continues when it errors out as anyways clck is working

Cheers