Deleting Disconnected and Unresponsive Unattended Sessions

This is how an administrator can delete disconnected and unresponsive unattended sessions from Orchestrator. As a result of this operation, Orchestrator is decluttered from unused sessions, which helps provide relevant insights to administrators by only showing connected sessions.

Note:

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.

Important:

We recommend deleting unattended sessions older than 60 days from your Sessions table.

Database maintenance for Orchestrator

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.