Job failed in Orchestrator

[Sonalk (Sonal)]

We are in Orchestrator Cloud and getting below error as job failed in Orchestrator. Triggers are setup in such a way to pick job by any available unattended robots.

Error details : Could not start executor. A specified logon session does not exist. It may already have terminated. (Exception from HRRESULT : 0x80070520).

I have also observed that job is in Pending state if bot is running another process job —> expected behaviour

Is this error arises because single bot is trying to run two different jobs at same point of time or another reason?

[nikhil.girish]

Hi @Sonalk

can you check this thread

A Specified Logon Session Does Not Exist - KB

How to troubleshoot if a Robot execution is failing with the following error: " A specified logon session does not exist. It may already have been terminated. " Executor start process failed, reason System.Runtime.InteropServices.COMException (0x80070520): A specified logon session does not exist. It may already have been terminated. (Exception from HRESULT: 0x80070520)\r\n " ? There can be different cause of the issue. Please follow the below options: Check the Operating system In case o…

hope this helps

[suraj.setty]

Hi @Sonalk

There could be some glitch,

When ever a Bot is busy with one Job and the trigger is set to run one more job the second job should be in the pending state until the bot completes first job.

If you are using an Enterprise License, please reach out to Ui Path Support.

[Sonalk (Sonal)]

Hi @suraj.setty : This is expected behaviour and jobs are currently working as expected.

I am getting this issue for 5 to 8 failed jobs only (in a day). This is my assumption that sometimes jobs are getting conflict and causing one job to run and other to get failed.

[Sonalk (Sonal)]

Hi @nikhil.girish : I tried to add timeout parameter but did not work for my case.

Thanks for sharing. I will go through all instructions again.

[Sreelatha278 (Sree Latha Reddy)]

Hello @Sonalk,

This might be a glitch. Sometimes restarting the Machine may help to resolve the issue.

[Sonalk (Sonal)]

Hi Everone : what is setting configured for unattended robots

Login to Console : Yes or No?

[nikhil.girish]

Hi @Sonalk

What is the purpose of Login to Console in orchestrator robot setting?

If LoginToConsole is true , the resolution is limited by the graphical card of the robot machine (which might be as low as 800x600 in some cloud environments), otherwise the resolution for a simulated RDP connection is restricted by RAM (which would generally be more permissive). Ref - Regards, Karthik Byggari

kindly go through the above post and select accordingly

[Sonalk (Sonal)]

Hi Nikhil : I have set this setting as ‘No’.

Multiple robots can simultaneously execute process or multiple sessions for same user.

[Sonalk (Sonal)]

Hi Everone : Issue is solved after cleaned up temp profile registries in Production server and restarted server.

[nikhil.girish]

Great @Sonalk

Happy Automation