Cannot run jobs from UiPath Orchestrator

Help
,
1

Hi,

I’ve been learning to use UiPath Orchestrator and have run into a roadblock.

I have created a machine, robot, process, and environment. Both the process and the robot are associated with the environment. I am able to run the process directly from the UiPath Robot on my PC after downloading it from Orchestrator. However, I am unable to run the process as a job via Orchestrator. The robot on the environment is not available to select when I try to run a job in Orchestrator.

Any advice would be appreciated. Thanks.

Job page

image
image1331×635 28.3 KB

2

@SimpleRookie

First you have to publish the package. First go to process tab and click add button to publish the package. After that go to job tab to run the process.

Cheers,
Lukas

3

Hello @SimpleRookie

You have to assign the robot to the environment. Go to the environment page and assign the robot to that environment. Then you will be able to see the robot in the create job page

1 Like
4

@Lahiru.Fernando

Thanks for the input. Unfortunately, unless I did something wrong I have already assigned both the bot(s) and the process to the environment. But the bots do not show up on the job screen when I try to run the process. Do you have any other ideas?

Bot(s)

image
image1680×254 25.6 KB

5

Thank you. I have already published the package and it is available on the process tab / assigned to the environment. If you have any other ideas, I would greatly appreciate it.

Process

image
image1683×268 16.2 KB

6

Hello @SimpleRookie

Is this the community version of the orchestrator you are using? or is it an enterprise edition?

If this is the community edition, Could you change the robot type to “Development” and try again to see whether it is showing in create job window?

7

Thank you! I changed the robot type to “Studio” and that worked.

Interestingly I did not have “Development” as a robot option, though I’m using the community license for studio/orchestrator. Do you know if there is a difference between the “Studio” and “Development” robot types?

1 Like
8

I think Studio is referred to the development robot type :slight_smile:

It’s just a matter of renaming… no worries… after all, it is working… :slight_smile:

1 Like
9

I am still facing the same issue though I have done everything which need to do.please give me some solution

startjob
startjob889×556 21.4 KB

1 Like
10

You need to add the robot and the process to the same environment inorder to execute a job

11

I am having the same issue. Did you resolved it?

12

I’m also having the same problem.

Robot type is studio and is active
Environment is set up and assigned to Robot
Job published
Added to processes
And I’m not using the robot to access a remote server.

Please help.

13

To run a robot from Orchestrator, it must be unattended type now (i.e. will not work for studio robot). Change the robot type via Robots/Edit in Orchestrator and it shall fly.

2 Likes
14

Same issue here. I tried to change robot type from Studio to Unattended but it says “No available licenses: the number of new machine slots would exceed the total license count. (#1916)”. Is orchestrator not anymore available for CE users? Appreciate your inputs. Thanks!

15

There is still 1 unattended license in CE, so it is probably in use by you elsewhere. Check your license page.

16

Seriously? This lack of this little piece of information cost me 2 hours… Thanks for sharing, though!

17

Additionally, it is necessary to provide ANY password when changing the type of the robot to unattended. It looked as if I was provided with a password immediately, however this password evaluated to null later (which I found out through looking at the failure details in the job). Thereafter, I deleted the “provided” password and typed in “password” instead. Now, everything is working fine.

2 Likes
18

Thanks, unfortunately it still cant be updated it to Unattended. I decided to do it again by deleting machines registered and adding again. Unfortunately, I can’t now connect to Orchestrator. I have provided Machine key correctly. It says “Invalid machine key”.

19

It’s now working. I found out 2 machines were active under License>Unattended. I just disabled the other one. Thanks!

20

I updated to unattended and re-entered the password and it’s running now.

Thank you for your help.