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

Help Orchestrator
,
10

The robot can run two jobs in a machine/VM using two separate user accounts. Mostly, we are not getting this error. For some jobs, we are getting the error specifically for a time. Let say, a job will be triggered 4 times a day. Out of 4 jobs, the 3rd job will always fails due to executor timed out issue. So, we changed the trigger timing a little and it sorted the issue.

A spreadsheet displays various job entries with details including start and end times, host machines, job states, creation times, and durations, highlighting one faulted job amid several successfully completed ones. (Captioned by AI)
A spreadsheet displays various job entries with details including start and end times, host machines, job states, creation times, and durations, highlighting one faulted job amid several successfully completed ones. (Captioned by AI)823×324 11.1 KB

In the attached image, you can able to see the highlighted job that was faulted due to the executor timed out error. There is no time conflicts and there was session free to that job. Is there a way to verify any open session in that VM?