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

[VanjaV]

Hi,

sometimes job is faulted because of:
System.Exception: Could not start executor. Creating user session timed out."

and sometimes the transaction will be set to “successful” after that.
I am using REFramework.

Any suggestions how to handle it?

Thx and KR, Vanja

[ashokkarale]

@VanjaV,

If this is intermittent issue, try to increase the timeout a little bit more than current time. Increase the UIPATH_SESSION_TIMEOUT system environment variable on the robot machine.

This could happen due to Slow Machine Performance due to high resource utilization (CPU, memory) or Network Latency as well. Look for the analysis on this as well.

@VanjaV

and sometimes the transaction will be set to “successful” after that.

This is strange because how transactions get’s picked up without executor starting up!

Also try this KB if not tried already

How To Troubleshoot The Error "Could Not Start Executor. Creating User Session Timed Out"?

Robots cannot run jobs and this error" System.Exception: Could not start executor. Creating user session timed out." is thrown. Summary: This knowledge base (KB) article offers insights into the problem, potential underlying causes, and a detailed troubleshooting guide for addressing the "System.Exception: Failed to start executor. Creating user session timed out" error that occurs when attempting to execute unattended jobs in Orchestrator. Symptom: The issue surfaces when initiating Robots …

[Anil_G (Anil Gorthi)]

@VanjaV

Generally this occurs when the system has latency or the availability on disk is low..as a first resort can you check those

Also checking event viewer logs might help in this case

Cheers

[VanjaV]

@ashokkarale

This is strange because how transactions get’s picked up without executor starting up!

Yes, this is really strange. That is also my question and not how to remove the error.

[ashokkarale]

@loginerror can you help here?