Can't run multiple jobs at the same time

[Sebastian_Jimenez_Chacon]

hello community,

I have a problem and it’s if I try to run the bot as unnatended with the “login to consolo” property as yes it works perfectly but that means I can’t run 2 or more jobs in parallel (different projects) so what can I do to run multiple jobs at the same time if I turn the property to “No” the job never start and only says : “System.Exception: Could not start executor. Creating user session timed out.”

[postwick (Paul)]

If the RDP session is timing out you need to work with your server team to figure out why.

Normally you don’t want to have “login to console” set to yes, exactly because you can only have one console session at a time. This is normal and can’t be changed.

[Sebastian_Jimenez_Chacon]

but how to figure out why it’s not running except by using the login to console property?

[TP2B (Tobias)]

On a Windows Server without any additional Terminal Server Licenses you can’t run more than 2 remote session. Have you reviewed the eventlog on this server?
Can you share some screenshots as I don’t understand exactly what you mean be run 2 Jobs in parallel?

[postwick (Paul)]

Work with your server team to review logs and find out why the RDP session is timing out.

[Anil_G (Anil Gorthi)]

@Sebastian_Jimenez_Chacon

Welcome to the community

Please check this

Getting error message 'Info: Could not start executor. Creating user session timed out.' since upgrading Robots to 2023.4.2

Run the below command in a powershell.exe console as Administrator: [Environment]::SetEnvironmentVariable("UiPath_SESSION_TIMEOUT", "500", "Machine") or Manually in Environment Variables [image]

cheers

[Palaniyappan (Forum Leader)]

@Sebastian_Jimenez_Chacon

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

To resolve the issue you may try these:

1. Remove the group policy that enforces MFA on the machine.

2. Check internally with your Network team to see why is taking so much time to connect your Robot to the Orchestrator server.

3. Increase the UiPath_SESSION_TIMEOUT system variable to 300 and restart the machine. This will allow more time for the second session to be established. If you don’t have that variable created, create it.

4. Make sure that the robot is not disconnected from Orchestrator.

5. In Orchestrator, edit your robot settings and enable the LoginToConsole to active and set its value to No, and make sure that the Robot machine is signed out (in a cmd.exe type logoff) before running the job from the Orchestrator.

6. Check if you installed the Robot in Service-Mode. For that in services.msc you should see UiPath Robot service running under a Local System account.

7. Check this documentation as well Robot - Frequently Encountered Robot Errors

Refer this thread for more details

Could not start executor. The wait operation timed out. (Exception from HRESULT: 0x80070102) RemoteException wrapping System.Exception: Could not start executor. The wait operation timed out. (Exception from HRESULT: 0x80070102)

This issue may happen when MFA (multi-factor authentication) is turned ON for the robot machine. Having MFA enabled on the machine doesn’t let the robot login into the machine and run workflows in Unattended mode. To resolve the issue you may try these: Remove the group policy that enforces MFA on the machine. Check internally with your Network team to see why is taking so much time to connect your Robot to the Orchestrator server. Increase the UIPATH_SESSION_TIMEOUT system variable to…

Cheers @Sebastian_Jimenez_Chacon