I’ve an odd situation, we have highly frequent scheduled jobs in our machine, one more than one job is scheduled for every 5mins. Recently I can see orchestrator is marking the job as failure without initiating the job in the client machine as the machine is busy in processing the previous job. Can anyone advice why orchestrator is reporting like this instead of keeping the job in queue/pending.
Below is the error we got.
Info: “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 at UiPath.UiSystemClass.OpenInteractiveWindowsSession(String bstrUser, String bstrPassword, UiOpenSessionFlags nFlags, String bstrApplication, String bstrAppArguments, Int32 nDelayMs, Int32 userToken, UiGenericOptions options)\r\n at UiPath.Core.Setup.OpenInteractiveWindowsSession(String username, String password, OpenSessionFlags flags, String application, String arguments, Int32 userToken, Int32 preferredWidth, Int32 preferredHeight, Int32 preferredDepth)\r\n at UiPath.Service.Impl.Executor.StartProcessInSession(Guid executorInstanceId, String username, String password, SettingsDictionary execSettings, IntPtr userToken)\r\n at UiPath.Service.Impl.Executor.<>c__DisplayClass15_1.<b__0>d.MoveNext()”