Job always pending when using trigger or manual run from orchestrator

Help Orchestrator
1

I try to create a test job, a simple one for claim epic games every 23:00, but when i try to set the trigger, the job is always pending, i currently using the computer, it can run from assistant, but cannot run from trigger or manual run orchestrator, please help

image
image2316Ă—311 45.4 KB

image
image1348Ă—1077 77.8 KB

note: i already set the time to match +7 utc 23:00

Forum Engagement Daily Reports
2

Hi @Hendaryie_Tjoeng
You have configured the trigger with Runtime type = Production (Unattended), but the selected machine is a personal laptop running with UiPath Assistant (Attended mode).

Unattended jobs cannot run on a user’s local machine. Orchestrator will keep the job in Pending state because it cannot find any available unattended robot to execute it

You can try this use unattended trigger

1 Edit the trigger
2 Change Runtime type to Attended
3 Make sure UiPath Assistant is running and you are logged in

The job will run only when the user session is active.

Pending status occurs because Unattended runtime is selected on a machine that only supports Attended execution.
Switching the trigger to Attended or using a proper Unattended VM will resolve the issue.

If it’s help please mark as solved and let me know if u still face the issue

3

Hi @Hendaryie_Tjoeng ,

You can check the following observations:

  1. A trigger can run only if an Unattended robot is available.

  2. Even if the trigger is created correctly, the job will stay Pending when:
    You are logged in and using the same machine
    The Unattended robot user/session is not free or not configured correctly

  3. How to run from trigger:
    Configure a proper Unattended robot in Orchestrator (user + machine + credentials)
    Log out of the machine (not just lock it)
    Make sure the machine shows Available / Connected
    Keep the trigger as Unattended

1 Like
4

Hi @Hendaryie_Tjoeng ,

This happens because the trigger is scheduled to execute with the “Unattended” trigger type, whereas an unattended robot has not been connected to the Orchestrator or is not available.

In the given screenshot, orchestrator shows:
0 Runtimes Available, 0 Connected

As a result, the job will remain in a pending state.

Why this runs from the UiPath Assistant

When using UiPath Assistant, the runtime type will be “Attended” and, Orchestrator trigger will not be triggered by an attended robot.

fix: (for personal pc or laptop)

  1. Edit the trigger.
  2. Change the Runtime (Production (Unattended)) runtime type to Attended.
  3. Ensure the user and the machine stay the same.
  4. Save the trigger.

Note:

  1. The user must be logged in.
  2. UiPath Assistant should be running.
  3. The screen should not be locked.
  4. For unattended jobs, proper unattended setup (license + connected machine) is required.
6

Hi @Hendaryie_Tjoeng
If solution helps you please mark as solved or let me know if you facing any issue.
Thanks

7

@Hendaryie_Tjoeng

if you see below unattended you would 0 available and connected

so you did not assign license to any mavhine..first assign license to machine

tenant → machines → unattended setup or edit machine and give a license

cheers