Orchestrator user guide

DELIVERY:

Last updated May 21, 2025

Deleting Disconnected and Unresponsive Unattended Sessions

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.

Note:

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.

Important:

In Automation Cloud^TM, a background job runs daily deleting old disconnected and unresponsive sessions as follows:

Automation Cloud^TM Community users - the background job removes three-month old disconnected and unresponsive unattended sessions;
Automation Cloud^TM Enterprise users - the background job removes six-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.