Job Stuck in Pending State – UiPath On-Prem Trial License

Help Orchestrator
, , , ,
1

Dear UiPath Support Team,

We are currently facing an issue where jobs are going into a Pending state when triggered from Orchestrator.

We have already completed the following steps:

  • Machine setup has been completed successfully.
  • Folder access has been provided to the respective user/robot.
  • Runtime license has been allocated.
  • The robot appears to be connected to Orchestrator.

However, when we execute the process from Orchestrator, the job remains in a Pending state and does not start running.

We are currently working with an On-Prem Trial license . Could you please advise if there are any additional configurations or checks required in this setup? Also, let us know if there are alternative approaches or troubleshooting steps we should follow to resolve this issue.

Looking forward to your guidance.

Thank you for your support.

Forum Engagement Daily Reports
2

@Chandru_S

In the targetmachine where the robot is installed..is the robot installed in unattended mode/service mode?

To confirm open machine → task manager → services → find UiPath.service.host service

If a userhost service is there it is installed in attended mode and jobs cannotbe started from orchestartor when machine is signed out

Cheers

3

Hello @Anil_G
Thanks for the response

Please find screenshot as we are using service mode and we try to execute process by keeping VM machine on

image
image663×591 22.8 KB

4

@Chandru_S

Go to automations..start a job and check if you are able to select an account and machine

Cheers

5

@Anil_G
we are able to select the machine and robot but still the process is showing pending

image
image1916×1076 170 KB

6

Looks you haven’t created the robot yet

7

@Chandru_S

Looks like you have given the machine license..can you confirm if the user is given robot role?

To confirm go to tenant → manage access → edit user check roles

Also can check if robot type shows as unattended in tenant → robots page

Cheers

8

Hi @Chandru_S

verify the machine template is mapped to the correct folder, ensure an unattended runtime is allocated and not consumed, check that the user is logged out for unattended execution, and validate that the process is published to the same folder where the runtime and machine are assigned.

Happy Automation

9

Go to Tenant → Manage Access → Edit User and ensure the user has the Robot/Unattended role with Execute permissions.
Check under Tenant → Robots that the robot type is set to Unattended.
Also verify the machine template has an Unattended runtime assigned.

10

Hi @Chandru_S

Could you please check if by any chance, maintainence mode is enabled on the machine you are trying to run your process?

When maintainence mode is on, processes stay in pending state untill it is lifted.

To check, go to tenant→ monitoring → unattended sessions → find your machine name and check if toggle is enabled?

image
image1561×408 52.6 KB

11

Hi @Chandru_S ,

You can check the following points -

  1. User Role & Permissions

    1. Go to Tenant → Manage Access → Edit User
    2. Ensure the user has Robot/Unattended role
    3. Confirm Execute permission is enabled

  2. Robot Type

    1. Go to Tenant → Robots
    2. Check that robot type is set to Unattended
    3. It should not be Attended if you are triggering from Orchestrator

  3. Machine Maintenance Mode

    1. Go to Tenant → Monitoring → Unattended Sessions
    2. Find your machine
    3. Check if Maintenance toggle is ON
    4. If enabled, disable it..

If any of the above is misconfigured, the job will stay in Pending even though the service is running and license is allocated …