orchestrator
latest
false
UiPath logo, featuring letters U and I in white

Orchestrator user guide

Last updated Feb 18, 2026

Trigger details

You can select a trigger from the list to check detailed information related to that trigger. Once selected, a side-panel is displayed with two tabs:
  • Jobs: you can check the list of jobs started by the trigger.
  • History: you can check the list of all instances when the trigger failed to start jobs.
  • Traces: you can view details about events received either through polling or webhook execution, as well as events that matched the selected trigger.
    Note: The Traces tab is only available for event triggers.

Jobs tab

To access the jobs started by a trigger:
  1. Navigate to the Triggers page.
  2. Choose the corresponding trigger tab.
  3. Select the relevant trigger from the list.
  4. Navigate to the Jobs tab to display the list of all jobs started by the selected trigger.
Note: You can use the Go to Audit button to navigate to the Audit page and check detailed information for each event. For more information, check the Audit page.
The table contains the following details for each job:
  • State: the current state of the job. For more information, check the Job States page.
  • Started: the timestamp when the job was started.
  • Ended: the timestamp when the job ended.
  • Duration: the total time the job run.

Trigger history

To access the list of all instances when the trigger failed to start jobs:
  1. Navigate to the Triggers page.
  2. Choose the corresponding trigger tab.
  3. Select the More Actions button
  4. Choose View history from the drop-down list.
    Tip: You can also select the needed trigger from the list and navigate to the History tab from the side panel.
Note: Trigger history is deleted when the trigger itself is deleted. Additionally, trigger history is retained for 30 days before it is automatically removed.
Note: You can use the Go to Audit button to navigate to the Audit page and check detailed information for each event. For more information, check the Audit page.
The table contains the following details for each trigger:
  • Time: the timestamp when the trigger failed to create jobs.
  • Failure type: the type of failure.
  • Description: a brief description of the failure.

Potential error types

Check the following list of potential failure types and their description:

Missing license

Description: a valid license is required to start jobs.

Solution: to continue running jobs, make sure that you have a valid license.

Expired license

Description: the license has expired.

Solution: to continue running jobs, you need to renew your license.

Disabled - job failures

Description: the trigger was disabled due to at least two consecutive job failures.

Solution: you can configure this setting using the Disable when consecutive job execution fail count option when creating or editing a trigger.

Disabled - consecutive failures

Description: the trigger was disabled after failing to create jobs a specified number of times within a defined number of days.

Solution: by default, this occurs after 10 failures in 1 day. You can configure this threshold by using the Triggers - Disable when job creation fail count and Triggers - Grace period when job creation keeps failing count (days) fields in conjuction from the Tenant Settings page. For more information, check the Settings page.

Pending jobs

Description: there are already pending jobs.

Solution: make sure that the process execution is not faulty, causing the job to remain in the pending state. You can also review the list of pending jobs and reduce the number of jobs if needed. For more information, check the Managing Jobs page.

Trigger error

Description: the trigger failed to create jobs.

Partial job creation

Description: only some jobs out of the total number of requested ones were created because there were already some pending jobs.

Solution: make sure that the process execution is not faulty, causing the job to remain in the pending state. You can also review the list of pending jobs and reduce the number of jobs if needed. For more information, check the Managing Jobs page.

Test job not supported

Description: test automation jobs are not supported through standard jobs APIs.

Robot not found

Description: no robot was found in the folder to run this job.

Solution: make sure that a robot is provisioned in the target folder. For more information on how to create a setup that allows you to execute jobs in folders, check the Managing Robots page.

Unattended robot not found

Description: no user with an unattended robot was found.

Solution: make sure that a robot is assigned to a user in the folder. For more information on how to assign a robot, check the Managing Robots page.

Trigger disabled

Description: the trigger is not enabled.

Solution: select the More Actions button on the corresponding trigger, and then Enable. An enabled time trigger is marked by the icon in front of it. An enabled queue trigger is marked by the in front of it.

No robot for user

Description: the user does not have a robot to trigger the event.

Solution: assign a robot to the user in the appropriate folder.

Process not found

Description: the process associated with the job could not be found.

Solution:
  • Check if the process is published.
  • Check if the process is created. If the process exists as a package, you need to create a corresponding process within Orchestrator
  • Check if the robot is connected and available in Orchestrator.
No machine available

Description: no compatible machine with runtimes was found.

Solution: make sure that:
  • Machines are not busy.
  • Machines have required licenses.
  • Machines are properly configured for the job.
User has no robot

Description: the user does not have an assigned unattended robot.

Solution: assign an unattended robot to the user. For more information on how to assign a robot, check the Managing Robots page.

Missing robot credentials

Description: missing credentials for the unattended robot.

Solution: add credentials depending on the chosen authentication method. For more information on how robot credentials work, check the Robot Authentication With Client Credentials page.

Callback not enabled

Description: the trigger requires a callback that is not enabled.

Solution: go to the API trigger and enable the callback.

Bad trigger config
Description: requests using the HTTP GET method cannot include a Content-Type header of type form or json.

Solution: adjust the trigger configuration to comply with HTTP method standards.

Traces

Important:

The information displayed in the Traces tab is available only for the most recent version of the trigger.

When you edit a trigger, the traces available for the previous version will no longer be visible in the Traces tab.

The Traces tab provides visibility into polling executions or webhook events received for an event trigger, including details about retrieved events and which of them matched the trigger filter criteria.

To access polling or webhook execution details and event information:

Note: This tab is only available for Event triggers.
  1. Navigate to the Triggers page.
  2. Choose the Event Triggers tab.
  3. Select the More Actions button
  4. Choose View traces from the drop-down list.
    Tip: You can also select the needed trigger from the list and navigate to the Traces tab from the side panel.

The Traces grid displays a chronological list of trigger execution records.

  • For polling triggers, each entry represents a poller execution.
  • For webhook triggers, each entry represents a webhook event received.

Each entry includes the execution start time and its outcome, allowing you to review trigger activity for a specific time.

Traces details

When you select a trace entry, the Details panel is displayed with the following information:

  • TriggerDetails: the following information is available for each trace:
    • traceID: a unique identifier for the trigger execution attempt.
    • timestamp: the date and time when the polling execution or webhook event occurred.
    • status: indicates whether the trigger execution was Successful or Failed.
    • dataReceived: indicates if event data was received during the trigger execution.
    • name: the name of the trigger.
    • eventType: the type of event that initiated the trigger (for example, FILE_CREATED).
    • filterExpression: the filter expression applied to the event, as configured for the trigger.
  • Data: provides technical details about how events were retrieved and processed during the selected execution.
    • Request: contains information about the request used to retrieve events during the polling execution or webhook handling.
      • query: the query parameters used for the polling execution.
      • path: the path (URL) to which the request was sent.
    • Response: an array of events received from the event source during the execution.

      • ID: the unique identifier of the event.

      • Created: the timestamp when the event was created.

      • Updated: the timestamp when the event was last updated.

  • DataFilter: when events are received, this section displays how the retrieved events were evaluated against the trigger filter expression.
    • Matched: the number of events that matched the trigger filter criteria.
      • ID
      • Created
      • Updated
    • Unmatched: the number of events that did not match the trigger filter criteria.
  • Jobs tab
  • Trigger history
  • Potential error types
  • Traces
  • Traces details

Was this page helpful?

Support and Services
Get The Help You Need
UiPath Academy
Learning RPA - Automation Courses
UiPath Forum
UiPath Community Forum
Uipath Logo
Trust and Security
Terms of Use
Privacy Policy
Cookies Policy
© 2005-2026 UiPath. All rights reserved.