Process running perfectly from Studio and also from UiPath Assistant while VM window is open, But Timeout error when running from Orchestrator as unattended process

[hacky (NotHacker)]

Hi Team,

I have completed my process development from the Studio.

While I was testing, following are my results:

• Running perfectly end to end from Studio as an attended robot
• Running perfectly end to end when ran from UiPath Assistant as an attended robot
• Running from Orchestrator as Unattended robot : Getting TIME OUT ERROR as soon as first instance of selector (click/type) appears

I can see the running from Orchestrator is giving TImeout errors as soon as selectors are involved into the automation.

I was able to observe this pattern, but not sure why this is happening.

Please help ASAP as this is affecting the production deliverables!!!

@supermanPunch @Palaniyappan @kirankumar.mahanthi1

Thanks and Regards,
hacky

[Gokul001 (Gokul Balaji)]

Hi @hacky

Have a view on this thread and check the Service mode type

Unattended but working only when the screen is open

Thanks a lot @seanrockvz13 for explaining to me about many things. After checking the whole system setting again . I have come to know that the path is installed with the Robot type as User Mode in the non-working VM . After the reinstallation is done with the robot type as Service Mode the VM is working fine. [image] If anyone faces the same issue you need to check this first in task manager->Details [image] There should be a Service. host available in the running state for unattended and…

Hope it works

Regards
Gokul

[kirankumar.mahanthi1 (Kirankumar Mahanthi)]

Hi @hacky ,

Could you please check below things first.

1. We should have any on going connections with the VM like user logins. to avoid this we have to restart the VM to make sure that no user logged into this VM machine.

2. Have you installed the Bot which you are running as un attended from orchestrator by using MSI installer since we must install the bot with service mode since service mode bot is required for un attended automation.

3. Make sure that you assigned un attended bot license for the Bot(VM) which you are trying to run your process un attended.

please check above points and let us share your confirmation. thanks.

[Palaniyappan (Forum Leader)]

Hi

Pls have a check on these points
Hope this would help you resolve this

1. I would strongly suggest you to follow the steps and guidance mentioned in this knowledge base which describes the same scenario you are facing
   Automation Works in Attended Mode but Not in Unattended Mode

2. Make sure the robot installed is in service mode
   This is very essential in order to let your bot run in unattended mode and also to access the UI elements

3. Finally Make sure the machine you developed and the machine where you are running this bot, has same resolution
   If the resolution of those machine differs then UI automation will fail
   Resolution can be set in ROBOT settings when you create your robot
   Set the same height, width properties between the machines

If you are using only one machine then it’s completely fine with this point in specific

Cheers @hacky