orchestrator

latest

false

Getting started
- Introduction
- Licensing
- Robots
  - Robot Statuses
  - Robot Settings
- Auto Updating Client Components
- Time-to-live Periods
- Orchestrator Outbound IP Addresses
- Autopilot chat in Orchestrator
- Notifications
Best practices
- Organization Modeling in Orchestrator
- Automation Best Practices
- Optimizing Unattended Infrastructure Using Machine Templates
- Unattended automation
- Organizing Resources With Tags
- Orchestrator Read-only Replica
- Exporting grids in the background
Tenant
- About the Tenant Context
- Searching for Resources in a Tenant
- Robots
- Folders
- Monitoring
- Access control
- Configuring automation capabilities
- Machines
- Solutions
- Packages
- Audit
- Credential Stores
- Webhooks
  - Types of Events
  - Managing Webhooks
- Licensing
  - Managing Your Licenses
- Settings
Cloud robots
- Unified Pricing licensing
  - Consuming platform units
  - Platform units calculation example
- Flex licensing
- Elastic Robot Orchestration
- Automation Cloud™ Robots - VM
- Automation Cloud™ Robots - Serverless
- Configuring VPN for cloud robots
- Configuring an ExpressRoute connection
- Live streaming and remote control
- My notifications
Folders Context
- About the Folders Context
- Home
Automations
- About Automations
Processes
- About Processes
- Managing Processes
- Managing Package Requirements
- Recording
- Live streaming and remote control
  - Live streaming and remote control via RealVNC
    - Error scenarios
  - Live streaming and remote control via TightVNC
    - Error scenarios
Jobs
- About Jobs
- Managing Jobs
- Job States
- Working with long-running workflows
- Running Personal Remote Automations
- Process Data Retention Policy
Apps
- About Apps
- Publishing an App to a Tenant
- Managing Apps
- Running a Deployed App from a Folder
Triggers
- About triggers
- Managing triggers
- Managing Non-Working Days
- Using Cron Expressions
  - Triggering jobs on the last day of the month
Logs
- About Logs
- Managing Logs in Orchestrator
- Logging Levels
Monitoring
- About Monitoring
- Machines
- Agents
- Processes
- Queues
- Indexes
- Queues SLA
Queues
- About Queues and Transactions
- Bulk uploading Queue Items using a CSV file
- Managing Queues in Orchestrator
- Managing Queues in Studio
- Managing Transactions
  - Editing Transactions
  - Field Descriptions for the Transactions .csv File
- Review Requests
Assets
- About Assets
- Managing Assets in Orchestrator
- Managing Assets in Studio
- Storing Assets in Azure Key Vault (read only)
- Storing Assets in HashiCorp Vault (read only)
- Storing Assets in AWS Secrets Manager (read only)
Business Rules
- About Business Rules
  - Permissions for Business Rules
- Managing Business Rules
  - Creating a business rule
Storage Buckets
- About Storage Buckets
  - CORS/CSP Configuration
- Managing Storage Buckets
MCP Servers
- About MCP Servers
- Managing MCP Servers
Indexes
- About indexes
- Managing indexes
Orchestrator testing
- FAQ - Deprecating the testing module
  - FAQ - Migrating test artifacts to Test Manager
- Test Automation
- Test Cases
  - Field Descriptions for the Test Cases Page
- Test Sets
  - Field Descriptions for the Test Sets Page
- Test Executions
  - Field Descriptions for the Test Executions Page
- Test Schedules
  - Field Descriptions for the Test Schedules Page
- Test Data Queues
- Testing Data Retention Policy
Resource Catalog Service
- About Resource Catalog Service
Integrations
- About Input and Output Arguments
  - Example of Using Input and Output Arguments
Troubleshooting
- About Troubleshooting
- Alerts troubleshooting
- General troubleshooting
- Frequently Encountered Orchestrator Errors

Orchestrator user guide

DELIVERY:

Last updated Aug 21, 2025

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.

Trigger history

To access the list of all instances when the trigger failed to start jobs:

Navigate to the Triggers page.
Choose the corresponding trigger tab.
Select the More Actions button
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.

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.