Session Creation Timeout (Unattended Robot)

Help Orchestrator
, ,
1

Hi UiPath Experts,

Thank you for your time and support.

I am encountering a low-level execution failure during unattended job initialization, specifically at the session creation phase. I would appreciate insights from anyone who has debugged similar infrastructure-level issues.

Error Details:
Executor could not be started. Timeout occurred while creating the user session.
System.Exception: Executor could not be started. Timeout occurred while creating the user session.

Currently, we have 4 processes with a total of 7 bots running on a specific VM. I would like to understand whether this setup could be causing the issue—particularly if resource contention or session limitations are preventing the bot from establishing a user session.

It would be very helpful if anyone who has faced this issue previously could share their experience, root cause analysis, or recommended troubleshooting steps.

Thank you in advance for your guidance.

Happy Automation!

2

Hello @Sandip_Shahane1,

Likely cause is session creation timing out due to VM constraints, not the workflow itself.

With 7 bots on one VM, concurrent starts can lead to:

  • CPU/RAM/disk contention delaying logon
  • RDP/session conflicts (stale or active sessions)
  • Windows session limits or policy restrictions

Quick checks:

  • First, please verify your C drive space and check if error screenshots in your project folder are causing storage pileup.
  • Stagger job start times (avoid simultaneous launches).
  • Ensure no disconnected/active RDP sessions remain.
  • Monitor CPU/memory/disk usage during job start.
  • Review Windows RDS/session policies.

Reducing concurrency is the fastest way to confirm if this is resource/session related.

Please review the documentation for more help: Robot - Execution troubleshooting

Thanks,
Karthik