orchestrator
2024.10
true
- 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
- SmartCard Authentication
- Configuring automation capabilities
- Audit
- Settings - Tenant Level
- Resource Catalog Service
- Folders Context
- Automations
- Processes
- Jobs
- Triggers
- Logs
- Monitoring
- Queues
- Assets
- Storage Buckets
- Test Suite - Orchestrator
- Other Configurations
- Integrations
- Host administration
- Organization administration
- Troubleshooting
Orchestrator User Guide
Last updated Nov 13, 2024
Job States
Jobs can have the following 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).
Running - A job is in this state if it has established a connection to the Robot which started executing the designated process.
Successful - A job is in this state if it has been executed correctly by the Robot and it has 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.- Stopping - An intermediary state that is triggered if you click the Stop button in Orchestrator. 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 that is triggered if you click the
Kill button in Orchestrator. By default, a cleanup background job runs
once every three hours and transitions to Faulted the jobs that have been in a
Terminating state for at least one day.
Suspended - An intermediary state that is triggered with the purpose of allowing user intervention or completion of an intermediary
process. It is triggered by the corresponding activities in Studio. Details here.
- Resumed - An intermediary state that is triggered if the conditions (user intervention, intermediary process completion) of a fragmented workflow have been met. It is triggered by the corresponding activities in Studio. Details here.
Stopped - A job is in this state if it stopped (by using the Kill button, or by canceling it from the system tray) before it finished executing without throwing any 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.
