Pending Jobs Turning Faulted After Restarting

[Korkmaz_Numan]

When my process that restarts on the server runs, other processes in the pending immediately faulted.
I was not experiencing this situation in version 2019.10.2. I encountered this situation after upgrading to version 2022.4.4.

error message:“Could not start executor. Rdp connection failed: Message: The disconnection was initiated by the user logging off their session on the server., Last error: 65548”

How can we make processes in pending without faulted when the connection is gone?

[Rahul_Unnikrishnan]

Does that mean whenever if you restart the server the jobs in pending state are moving to faulted?

Please check the below post as well.

Robot disconnects after each job causing next pending job to fail

Normally if a job is in queue from orchestrator - it is supposed to show pending status and once previous job finishes, the queued job will start executing. But in my case,if there is a queued job, it will fail since the bot logs off and logs in again after each job. Each time it logs off , it shut downs the robot service which causes next job to fail immediately. Note: I am using enterprise edition, Robots are in VDI’s. (There are multiple logins in same vdi based on each job -so bot is suppo…

Thanks

[J0ska]

Facing the same issue

Pending job fails on robot disconnect

Hi, environment: orchestrator and only one robot imagine following scenario: JOB1 starts another job using Start Job sctivity. It results in one running (JOB1) and one pending job (JOB2). Before JOB1 finishes the robot machine disconnects. It results in JOB1 failure with error “Job stopped with an unexpected exit code: 0x40010004” Orchestrator starts pending JOB2 despite the robot is disconnected JOB2 immediately fails with error “Could not start executor. Rdp connection failed: Message:…