Hello folks, I have a bot scheduled from every day from 9 am to 10 pm. For initial run at 9 am it is throwing up error saying Timeout reached. I could see that Terminal server got disconnected from local and I am under impression that bot would be running in background even If it’s get disconnected…

Could you provide more details like is this using version 2018 and is it an Attended or Unattended? Also, do you notice anything else that occurs when this happens, like is it only happening when the Attended machine is locked? I think this error is caused when the session loses its GUI like when y…

@ClaytonM Hey Clayton! Thanks for swift response. I am using Orchestrator version 2018.4.1 and it is unattended bot. This issue is happening only in morning for 1st run and once the screen is unlocked, there won’t be any issues. Literally I have to be online on Terminal Server to avoid this issue fo…

Usually with unattended, the robot will log in to create the session without anyone else (human) logging in to that session. Once the robot finishes a process, it will end the login session. It sounds like you are trying to log in to the session manually, then run the robot? You can do this, but yo…

Timeout error whenever Terminal server gets disconnected

Help

srinucslt (Srinu) April 5, 2019, 8:21pm 5

Resolved this issue by enabling “Login to console” on Orchestrator.

Connection between mainframe and terminal session

Topic		Replies	Views
"Timeout reached" error when RDP is disconnected Help orchestrator , robot	11	6301	May 15, 2019
Unattended Robot does not taking session schedule through orchestrator Help orchestrator , error	2	967	December 9, 2019
Unattended Bot (scheduled every hour) is pending Orchestrator orchestrator , question	3	700	February 2, 2021
Unattended Bot behaving as an Attended Bot Robot unattended	5	867	April 24, 2023
Timeout reached when the remote desktop is not connected Robot unattended	16	5073	November 14, 2021

Timeout error whenever Terminal server gets disconnected

Related topics