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

Help Orchestrator
,
1

Some jobs is getting the “Could not start executor. Creating user session timed out.
System.Exception: Could not start executor. Creating user session timed out.” and gets faulted. Can anyone help me why this is happening and how UiPath orchestrator starts or signal UiPath robot to login. Is there a option to make sure that the robot signout/close the created session?

2

@john.mari can you check and make sure for robot user in orchestrator the login to console option is set as No

3

Hi @john.mari

Does this happen everytime for you or random instances?

4

The robot will sign out of the created session, unless a human logged in and then closed the RDP window without signing out. Then the session is left open, even after a robot uses the session.

5

@john.mari,

Refer this knowledgebase for the possible reason and solution.

6

Hi @john.mari

Please try to increase the session timeout, close apps properly, monitor system resources, and manage disconnected sessions.

If you found helpful, feel free to tick as a solution.
Happy Automation

7

@Darshan_Sable The login to console is already set to no

8

It is happening random. We can’t find a pattern.

9

@prashant1603765 We set the UiPath_SESSION_TIMEOUT to 500 or 600. How can we manage the disconnected sessions using UiPath. Do we need to connect with the IT team to implement?

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?

11

Hi @john.mari

Which version of studio you are using?

We had also faced this issue quite a lot in our org.

So, below 2 solutions helped us:

  1. upgrading to UiPath version 24.10.6 → this was suggested by UiPath after we had raised ticket to UiPath for our time out issue.
  2. deleting the temp files from the VM/machine. For all of our VMs where this issue was happening, space was also the issue for us. Liberating space there helped us greatly.

Please try to see if any of these work for you as well.

Regards
Sonali

12

@sonaliaggarwal47 We are using the UiPath robot v2023.10.3. Sure, I will try the workaround and update here

13

Maybe server resources are low.

14

Might be configuration issue, Better if you can connect with the IT team .

Happy automation