orchestrator
latest
false
Orchestrator user guide
- Getting started
- Best practices
- 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
- Settings
- Registry
- Cloud robots
- Automation Suite Robots
- Folders Context
- Processes
- Jobs
- Apps
- Triggers
- Logs
- Monitoring
- Indexes
- Queues
- Assets
- Connections
- Business Rules
- Storage Buckets
- MCP Servers
- Orchestrator testing
- Resource Catalog Service
- Integrations
- Troubleshooting
Jobs transition through various states during their lifecycle, as described below.
Initial States
Pending - A job is in this state if it is queued on the same Robot or it is trying to establish a connection with the Robot (only different jobs on the same Robot can be queued).
Active States
Running - A job is in this state if it has established a connection to the Robot which started executing the designated process.- Stopping - An intermediary state triggered when you select Stop. The job is canceled as soon as it is safe. This can be implemented in a workflow using the Should Stop activity.
- Terminating - An intermediary state triggered when you select Kill. A cleanup background job runs once every three hours and transitions to Faulted jobs in a Terminating state for at least one day.
Intermediate States
Suspended - An intermediary state allowing user intervention or completion of an intermediary process. Triggered by corresponding activities in Studio. Details here.- Resumed - An intermediary state triggered when conditions (user intervention, intermediary process completion) of a fragmented workflow are met. Triggered by corresponding activities in Studio. Details here.
Completion States
Successful - A job is in this state if it has been executed correctly by the Robot and finished running or has been stopped using the Stop button.
Faulted - A job is in this state if it failed to start or the process threw an unhandled error during execution.
Note:Faulted jobs must be restarted manually.
Stopped - A job is in this state if it stopped (by using the Kill button or by canceling it from the system tray) before finishing without errors.
To view more information about all job executions, click the corresponding Details button. The Job Details window is displayed and enables you to view why a job faulted. Additionally, for unattended faulted jobs, if your process had the Enable Recording option switched on, you can also download the corresponding execution media and check the last moments of the execution before failure.