- 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
This section provides instructions on how an administrator can delete disconnected and unresponsive unattended sessions from Orchestrator. This operation de-clutters Orchestrator from unused sessions, which helps provide relevant insights to administrators by only showing connected sessions.
-
You need the Delete permissions on Robots to delete unattended sessions.
-
When attempting to delete unattended sessions that have triggers attached, a dialog appears, displaying the number of triggers attached to each session, and you must confirm the deletion by entering a confirmation text string in the Confirmation for removal field. For unattended sessions that have time triggers or queue triggers attached, the following scenarios are recorded in the audit log and result in notifications:
- A session deletion results in an enabled trigger not being assigned to any machine. In this case, the trigger is disabled, and you receive a Trigger automatically disabled notification.
- A session deletion results in an enabled trigger being unassigned from some but not all the machines to which it was assigned, or a disabled trigger not being assigned to any machine. In this case, you receive a Trigger configuration was changed notification.
Removing disconnected and unresponsive unattended sessions allows de-cluttering the Unattended Sessions view and helps provide relevant insights to administrators by only showing connected sessions.
- Disconnected session - the robot was gracefully stopped;
- Unresponsive session - the robot did not successfully send a heartbeat four times in a row.
The Unattended sessions window shows separate entries for each license type associated with one session, so you might see multiple rows for the same session, one for each license type. Upon removal of one of those entries, all the other entries are removed as well.
Sessions table.
To remove the unattended sessions one by one, follow these steps:
- Navigate to Tenant > Monitoring > Unattended sessions.
- For the disconnected or unresponsive session you wish to remove, click More actions > Remove.
- Click Delete to confirm the deletion when prompted. The unattended session is removed from the Unattended sessions view and the Installed Versions & Logs window.
To remove multiple unattended sessions simultaneously, follow these steps:
- Select the disconnected or unresponsive unattended sessions and then click the Remove icon.
- Click Delete to confirm the deletion when prompted. The unattended disconnected sessions are removed from the Unattended sessions view and the Installed Versions & Logs window.
