- Organization Modeling in Orchestrator
- Automation Best Practices
- Optimizing Unattended Infrastructure Using Machine Templates
- Organizing Resources With Tags
- Orchestrator Read-only Replica
- Exporting grids in the background
- 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
- Elastic Robot Orchestration
- Automation Cloud™ Robots - VM
- Automation Cloud™ Robots - Serverless
- Configuring VPN for Cloud Robots
- Bulk Uploading Queue Items Using a CSV File
- Managing Queues in Orchestrator
- Managing Queues in Studio
- Review Requests
- Test Automation
Deleting Disconnected and Unresponsive Unattended Sessions
This article walks administrators through the instructions for deleting disconnected and unresponsive unattended sessions from Orchestrator. This operation allows declutter Orchestrator from unused sessions and helps provide relevant insights to administrators by only showing connected sessions.
You need Delete permissions on Robots to delete unattended sessions.
You can only delete sessions with no trigger attached.
Removing disconnected and unresponsive unattended sessions allows decluttering 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 4 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.
In Automation Cloud, a background job runs daily deleting old disconnected and unresponsive sessions as follows:
- Automation Cloud Community users - the background job removes 3-month old disconnected and unresponsive unattended sessions;
- Automation Cloud Enterprise users - the background job removes 6-month old disconnected and unresponsive unattended sessions.
Removing Unattended Sessions Individually
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.
Removing Multiple Unattended Sessions at Once
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.
Removing unattended sessions is audited on the Audit page using the Sessions component.