Could not start executor. Creating user session timed out

Help StudioX
, ,
1

Could not start executor. Creating user session timed out.

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

we added the environment to 600 seconds but cant start the executor
Last session took 10 minutes
image

But if we connect to the VDI and then logout its works
What settings here im missing !

Br/Hazem

2

Hi,

Attaching the below thread for your analysis

3

Thanks we seems having the same issue 2023.4.2 :confused: i will follow that topic thanks for sharing

4

Is issue resolved at your end @Hazem_Saleh

5

Hi yes
we found a text message block the executor :slight_smile:

Br/Hazem

6

Which text message… Can you help to understand what you did to fix the issue?

7

@Ashish32229,

There was a message box activity used in the workflow, which shows a popup message. It will not go away until and unless configured accordingly or closed manually.

8

Where do we need to configure that?

9

@Ashish32229,

I would advise to not to use Message box in unattended bot’s. To log something use Log message.

If you still want Message Box configure it’s property AutomaticallyCloseAfter to your desired timeframe.

image
image1060×240 16.4 KB

Thanks,
Ashok :slight_smile:

10

Hello @ashokkarale and @Hazem_Saleh ,

I have the same problem happening, but I don’t have any “Message Box” Activity in my bot. It must be some other activity that is causing the issue…if you could tell me how you found out it was the Message Box activity, maybe I can do the same and find what activity it is in my bot. Thank you

11

@ashokkarale - There is no message activity in my code as it’s unattended solution. Not sure if you referring to correct activity.

12

Hi ,
sorry for late answer its info message always show up when the robot login

13

its from windows not the robot.

14

Increasing UiPath Session Timeout has resolved the issue. So there is nothing related to message box or logging which blocks it.

15

If it helps anyone, I logged into the machine and accessed the Assistant as a developer to view the automations. (I logged in since i couldn’t run an automation from the Assistant since it was installed as unattended.) I then ran an automation and simply closed the machine. It worked afterward. I hadn’t updated the machine or studio/assistant on the machine recently. We use Cloud Orchestrator, and this issue happened randomly.

16

I found we have extra screen on our AVD, its will tell the last login time,
UiPath can skip that so you might have it as well.
BR/Hazem