Timeout reached

Hy I have this error when job start .

An ExceptionDetail, likely created by IncludeExceptionDetailInFaults=true, whose value is:
UiPath.Core.ElementOperationException: Timeout reached. ----> System.Runtime.InteropServices.COMException: Timeout reached.
at UiPath.UiNodeClass.BringIntoView()
at UiPath.Core.UiElement.BringToForeground()
— End of inner ExceptionDetail stack trace —
at UiPath.Executor.WorkflowRunner.EndExecute(IAsyncResult result)
at UiPath.Core.Activities.InvokeWorkflowFile.EndExecute(AsyncCodeActivityContext context, IAsyncResult result)
at System.Activities.AsyncCodeActivity.System.Activities.IAsyncCodeActivity.FinishExecution(AsyncCodeActivityContext context, IAsyncResult result)
at System.Activities.AsyncCodeActivity.CompleteAsyncCodeActivityData.CompleteAsyncCodeActivityWorkItem.Execute(ActivityExecutor executor, BookmarkManager bookmarkManager)

Hi @alexadrupavel,
Welcome to the Community!
Please give us more details. What job are you starting? Is this message coming from Studio or Orchestrator? Does this issue occur for any other processes? Please explain little bit more.

As far as I understand, you are trying to do automation in remote desktop.

So this exception occurs when you minimise the remote desktop while the robot is executing.

Hence the exception clearly says “.UiElement.BringToForeground()”. Ensure that your remote desktop is not minimised or disconnected to avoid this issue.

Hope this helped you, if so kindly mark this as solution.

interesting
I did not think it registered as a remote control connection.
so I have to redo the process directly from the computer so I will not have any problems.

Can I remove this element?

When I run robot from computer is run ok.
When is run in Orchestrator I have this error. But not every time.

An ExceptionDetail, likely created by IncludeExceptionDetailInFaults=true, whose value is:
UiPath.Core.ElementOperationException: Timeout reached. ----> System.Runtime.InteropServices.COMException: Timeout reached.
at UiPath.UiNodeClass.BringIntoView()
at UiPath.Core.UiElement.BringToForeground()
— End of inner ExceptionDetail stack trace —
at UiPath.Executor.ExecutorRunner.EndExecute(IAsyncResult result)
at UiPath.Core.Activities.InvokeWorkflowFile.EndExecute(AsyncCodeActivityContext context, IAsyncResult result)
at System.Activities.AsyncCodeActivity.System.Activities.IAsyncCodeActivity.FinishExecution(AsyncCodeActivityContext context, IAsyncResult result)
at System.Activities.AsyncCodeActivity.CompleteAsyncCodeActivityData.CompleteAsyncCodeActivityWorkItem.Execute(ActivityExecutor executor, BookmarkManager bookmarkManager)

Which version of Studio and Orchestrator are you using?

2019.5.0

Orchestrator 2019.5.0-CE.21

Please have a look here:


There was a similar problem with process which was running through RDP. Maybe it will help.

it’s work just if I am connect on RDP.
If I am logout the robot have error

Hi Alex,

did you found a solution? We are having the same issue here, and we are running our processes with the latest version… (2020.4.1)

Thanks

It all depends on which robot has been used (attended/unattended) and if all properly set. Additionally you need to remember that in case of RDP automation UiPath Assistant (Robot) should be installed using Enterprise Installer to have the all possibilities of use unattented solutions.
More information here:


1 Like

Hi guys, @Pablito

I’ve been reading similar posts like this, and I’ve to say that sometimes I’m facing the same problem.

I dont really know what is the main reason for it, but in my scenario, I have to login in a webpage which has a pre-login before, in which you have to enter the same credentials as login, and its the tipical window popup merging from the top.

When I run my processes in a RDP session with the screen opened (also if I run them from my laptop) they work fine. Actually, in unattended session is working fine almost everytime, but I’ve to say that sometimes that login fails, giving me the famous message: “Timeout reached… UiPath.UiAutomation.Activities”

Its easy to solve the problem for me, because I just have to relaunch the process from Orchestrator again.

But there is another weird key too. If that fail happens, if I retry the login “X” times (no matter how much) without ending the process and relaunching it again form zero like a new process, it still failing again and again.

Maybe this info could be helpful. I’m here for whatever guys.

KR,
Pablo

Hi @Pablo_Sanchez,
Your case look similar but I’m not sure if the background of an issue is different. I think in your case the reason might be related to the situation where the website is loaded to fast or to late and some activities couldn’t react properly. You could experiment with the “Element exists” activity or the “wait for ready” property.

1 Like

Sorry for my English as I use a translator.

I often encounter this problem and it is related to the fact that during the robot’s operation you were connected to its machine via RDP and the moment when the robot communicates with any interface not via a simulite or windose. Your RDP connection has been terminated and/or you have disconnected from the main PC and there is still an RDP connection left.

This problem is solved by using simulite clicks or simply by not disconnecting when the robot is working with the web interface.

Moderated