orchestrator
2.2510
false
- Getting started
- Best practices
- Organization Modeling in Orchestrator
- Managing Large Deployments
- Automation Best Practices
- Optimizing Unattended Infrastructure Using Machine Templates
- Organizing Resources With Tags
- Orchestrator Read-only Replica
- Exporting grids in the background
- Enforcing user-level Integration Service connection governance
- Tenant
- About the Tenant Context
- Searching for Resources in a Tenant
- Managing Robots
- Connecting Robots to Orchestrator
- Storing Robot Credentials in CyberArk
- Storing Unattended Robot Passwords in Azure Key Vault (read only)
- Storing Unattended Robot Credentials in HashiCorp Vault (read only)
- Storing Unattended Robot Credentials in AWS Secrets Manager (read only)
- Deleting Disconnected and Unresponsive Unattended Sessions
- Robot Authentication
- Robot Authentication With Client Credentials
- Configuring automation capabilities
- Solutions
- Audit
- Resource Catalog Service
- Automation Suite Robots
- Folders Context
- Automations
- Processes
- Jobs
- Apps
- Triggers
- Logs
- Monitoring
- Queues
- Assets
- Storage Buckets
- Indexes
- Orchestrator testing
- Integrations
- Troubleshooting

Orchestrator user guide
Last updated Nov 11, 2025
To access the jobs started by a trigger:
- Navigate to the Triggers page.
- Choose the corresponding trigger tab.
- Select the relevant trigger from the list.
- 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.