Timeout reached - Troubleshoot steps

Help
1

Description

UiPath.Core.ElementOperationException: Timeout reached. —> System.Runtime.InteropServices.COMException: Timeout reached.

Troubleshooting steps

The error “Timeout reached” occurs when the robot is waiting for some elements to come on the screen and the element is not available on the screen even after the 30sec(default). It might be possible that though the visuals of the elements are available but the background code of the element is not fully loaded in the system.

Majority of such issues any user faces when the resolution configuration is not defined for the specific Robot. And the behavior would be the moment you open up the Robot server - the process would run end to end without any issue.
How to apply the resolution configuration

Also, below guides to improve your developed code

Please follow the below approach:

  • You can increase the time out amount in the field " Timeout ".

  • Use the activity " Element Exists " before performing the specific action on the element (like Click) so that you get to know whether the robot is able to detect the element or not.

  • If you are using some activity that has the property of " WaitForReady ", then try with the setting of " None / COMPLETE ".
    ​

  • Use the " Retry " activity to retry the automation in case it fails.

  • Please check the sendwindowMessages/ SimulateClick option in properties panel & Verify :
    ​

  • Use the activity “Take Screenshot” + “Save Image” to capture the image of the screen.
    In this way, you can visualize what the robot is viewing.

  • As you running the robot in unattended mode.Please set the value of “LoginToConsole” to “false” in the %ProgramData%\UiPath\UiPath.settings file. Please follow the steps mentioned in the below link:
    Resolution settings / UiPath.Settings File resolution configuration / runtime resolution - unattended configuration - How To

Kindly share the outcome after applying all the above settings.

(Modifying the workflow as per the above recommendation should fix the current timeout issue)

4 Likes
2

I have Take screen shot and save image, and retry the process, but as soon as it get below exception
{
“message”: “Exception : UiPath.Core.ElementOperationException: Timeout reached. —> System.Runtime.InteropServices.COMException: Timeout reached.\r\n at UiPath.UiNodeClass.BringIntoView()\r\n at UiPath.Core.UiElement.BringToForeground()\r\n — End of inner exception stack trace —\r\n at UiPath.Core.Activities.ScopeActivity.OnFaulted(NativeActivityFaultContext faultContext, Exception propagatedException, ActivityInstance propagatedFrom)\r\n at System.Activities.Runtime.FaultCallbackWrapper.Invoke(NativeActivityFaultContext faultContext, Exception propagatedException, ActivityInstance propagatedFrom)\r\n at System.Activities.Runtime.FaultCallbackWrapper.FaultWorkItem.Execute(ActivityExecutor executor, BookmarkManager bookmarkManager)”,
“level”: “Information”,
“timeStamp”: “06:16:08”,
“processVersion”: “1.0.6943.9969”,
“fileName”: “Process”,
“jobId”: “d3972cf6-e1c3-45ee-b670-1e9e2d537c69”,
“robotName”: “*”
}

bot is not even responding, not even going to next activity I.e, Take screenshot.

1 Like
3

Hey Divya @Divyashreem Did you resolved this issue?

6

@srinucslt - I had same issue for image based activity run via task scheduler when user is disconnected. It is working fine when user session is active and connected.

7

Note: Minimizing the desktop window / Login to the Robot server when the process is being executed in unattended mode / Disconnecting the Robot session - It’s not supported.
Also, scheduling jobs using Task Scheduler is not supported.
Please use Orchestrator .

2 Likes