How to configure processes to run with any available machine on orchestrator?

Help Orchestrator
, , , ,
1

I have setup a event trigger of office 365 outlook - to run the a process on receiving a mail with a particular subject line. This trigger is working fine.

Now my challenge is to run the process at any available machine.

I am not sure how this is possible? Will there be any conflicts in hostname , machine or account dynamic selection. Not sure how to configure process to run with any available machine. Thanks in advance.

2

Hi @Eshu_Dhiman

Let’s say you would like your automation to run on machine A or machine B.

So in this case, you can have machine A and machine B both added to the folder from wheeler automation will be running.

Bot will pick any available machine of the two assigned to the folder.

Likewise goes for bot account, if you have multiple robots assigned to the folder, it will be automatically picked.

So no need to select any particular machine or bot under machine name or account.

Hope this helps.

Regards
Sonali

3

Hi @Eshu_Dhiman ,

No need to setup any extra settings. Process will be always triggered on any free machine from machines assigned in the folder.

4

Hi @Eshu_Dhiman

The image is a flowchart outlining the steps for setting up a modern unattended automation system, detailing processes related to Machines, Users, Folder management, and Processes. (Captioned by AI)
The image is a flowchart outlining the steps for setting up a modern unattended automation system, detailing processes related to Machines, Users, Folder management, and Processes. (Captioned by AI)1920×789 56.4 KB

Pls check this for more,

If helpful, mark as solution. Happy automation with UiPath

5

@Darshan_Sable & @sonaliaggarwal47 Thankyou for the response.
Hostnames are being picked randomly resulting in this error:

Could not start executor. Logon failed for user “username”. Reason:
ERROR_ACCOUNT_RESTRICTION=ERROR_ACCOUNT_RESTRICTION=0x0000052F : Account restrictions are preventing this user from signing in. For example: blank passwords aren’t allowed, sign-in times are limited, or a policy restriction has been enforced.

ERROR_INVALID_WORKSTATION=ERROR_INVALID_WORKSTATION=0x00000531 : This user isn’t allowed to sign in to this computer..

Please help.

6

Can you please refer below post on same error?

7

@Eshu_Dhiman

Also can you check your robot credentials(username/passwors)

It can be the case it’s not updated correctly.

8

HI @sonaliaggarwal47 That is the case different hostnames have different passwords. How can we tackle that?

9

That is fine.

We just need to ensure that passwords for all bots are updated for their account in orchestrator.

You should be able to navigate to tenant->manage access , find your bot account and update the password there.

Now which ever bot is picking up your process, corresponding credentials will be used.

10

I think the user account has login restrictions , limited sign-in times or pls update sign-in policies on the machines.

Happy Automation

11

Also check if you have specified robot username as
Domain\username

Or username?

If you are not sure of the domain, login manually to machine using your bot account where you are trying to run your automation.

Go to command prompt, run command

Whoami

It will provide you the username that you need to specify on orchestrator.

12

@Eshu_Dhiman

Either create user account malpings

Second makesure any user can use any machine and configure passwords for all users

Either one of the above two should be done

Cheers

13

Hi @Anil_G , Thanks for the reply, Can you please walk me through the steps ? Thanks in advance.

14

@Eshu_Dhiman

Detailed steps are here

Cheers

15

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.