Scheduler job fails after time of inactivity

[Mateusz_Majchrzak]

Hello!

Recently, we’ve started experiencing an uncommon issue with scheduled jobs.

What is happening:
1st job from scheduler keeps failing after time of inactivity. The next job scheduled after that and subsequent ones run just fine.

Description:
When the difference between the last run job and the next one is about an hour or larger, it causes the first and only first scheduled job to fail. If we have other jobs coming after that, they will run fine. The error that we are seeing is the following:

Could not start executor. Creating user session timed out.
System.Exception: Could not start executor. Creating user session timed out.

Any suggestions what might be causing it? We’ve tried so far to increase UiPath_SESSION_TIMEOUT, logging out all users from the VM and more.

Thanks!

[monsieurrahul (Rahul)]

Check this:

Executor start process failed. "Could not start executor. A specified logon session does not exist."

Hi UiPath Users/Team, We are currently experiencing problem with scheduling jobs failing to start intermittently for the unattended bots. Below is the error we could see. Could not start executor. A specified logon session does not exist. It may already have been terminated. (Exception from HRESULT: 0x80070520) Our scheduled job runs every 15 min. In a day we see this error probably 10-11 times. We had to restart the process everytime we see this error. Below are the Robot settings: Logging…