My command for my robot gets sent but it doesnt run?

[Jorgeluis_Mijares]

I try to start a process and the command gets sent but it doesnt run, in the jobs section it says pending. I can run it in UiPath assistant but I want to be able to run it through orchestrator. Please help!

[Gokul001 (Gokul Balaji)]

Hi @Jorgeluis_Mijares

You can check the machine and User are set correctly

If you have Unattended license check the below Thread

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…

Regards
Gokul

[nikhil.girish]

Hi @Jorgeluis_Mijares
You need to change the Robot License to Unattended. Jobs From Orchestrator can be started with an Unattended License.

Thanks

[THIRU_NANI (NaNi)]

Hi!

I hope you have connected your machine with robot. if not try this.

1.Tenant->Manage Access->Select your account->Edit->Robot Setup->Run Foreground automation

provide the following

Domain/Username

Win+R → TYPE whoami->copy the code and provide it in Domain/Username

Credential store

Orchestrator Database

Password

Your windows password

Credential type

Windows credentials

Then click on save.

Inside the studio:

please follow the below steps:

1.Signout from studio and UIPath Assistant.
2.Now close studio
3.Now open the UiPath Assistant Navigate user Icon ->Preferences->Orchestrator settings->Sign in

this will automatically sign in both Studio and Assistant.

now publish the workflow

now open your cloud account

Navigate to the Workflow folder in cloud

then navigate to Automation->process->Add process
you may see your published workflow here
Navigate to Jobs->Add jobs run your workflow

Regards,
NaNi

[jeevith (Jeevith Hegde, Ph.D.)]

Hi @nikhil.girish,

Just to clarify : Jobs can also be run from orchestrator if you have a testing robot license or a non production license. Does not specifically have to be unattended license.

[Shikhar_Tandon]

Hi @Jorgeluis_Mijares,

Welcome to the community!

The issue depends upon the environment you are working. I am supposing it be production.

First of all in the jobs section click on the details legend of that particular job to check the message which can be like “Robot licensing failed” or anything else.
If licensing is failed first check the robot type, should be unattended if robot is absolutely fine. Go to licenses section and check if the license utilization is not 100%, if that is also correct then login the machine you are trying to run the bot on and click Win+R, run will pop up, type Logoff in the box and hit enter and check if the job runs.

Thanks

[nikhil.girish]

Exactly @jeevith we should have any among these