- Getting started
- Best practices
- Tenant
- About the Tenant Context
- Searching for Resources in a Tenant
- Managing Robots
- Connecting Robots to Orchestrator
- Setup Samples
- Storing Robot Credentials in CyberArk
- Setting up Attended Robots
- Setting up Unattended Robots
- Storing Unattended Robot Passwords in Azure Key Vault (read-only)
- Storing Unattended Robot Credentials in HashiCorp Vault (read-only)
- Deleting Disconnected and Unresponsive Unattended Sessions
- Robot Authentication
- Robot Authentication With Client Credentials
- SmartCard Authentication
- Unattended Sessions
- User Sessions
- License
- Audit
- Resource Catalog Service
- Folders Context
- Automations
- Processes
- Jobs
- Triggers
- Logs
- Monitoring
- Queues
- Assets
- Storage Buckets
- Test Suite - Orchestrator
- Other Configurations
- Integrations
- Classic Robots
- Host administration
- Organization administration
- Troubleshooting
Unattended Sessions
This section offers an overview of all unattended sessions and related information.
|
Column Name |
Description |
|---|---|
|
Hostname |
The name of the host machine. |
|
Machine |
The machine template used to connect the corresponding host machine to Orchestrator. |
|
Runtimes |
The number of runtimes associated with a machine template. Each host machine connected using that machine template secures this number of licenses from the tenant's pool of licenses. |
|
In Use |
The number of runtimes currently being consumed out of the number of runtimes secured on that host machine. A runtime is consumed during job execution. |
|
Runtime type |
The type of license. |
|
Service username |
The identity under which unattended jobs are executed. For service accounts, this is empty. |
|
Status |
The connection status of each host machine. |
|
Last Heartbeat |
Time elapsed since the last heartbeat. Hover over this field to see the exact time of the last heartbeat. |
|
Troubleshooting |
Indicates if the corresponding unattended session has a troubleshooting session enabled. |
