Orchestrator
latest
false
- 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
- Audit
- Settings
Orchestrator User Guide
Last updated Nov 30, 2023
Time-to-live Periods
Time to live (TTL) determines how long certain Orchestrator data is stored in the database before being discarded.
The TTL policy depends on your subscription plan and data type. Data older than the corresponding time-to-live is deleted from our Orchestrator database.
Time-to-live Periods
Data expires once it exceeds the TTL period as follows:
Data Type |
Community |
Enterprise |
---|---|---|
Disconnected and unresponsive unattended sessions |
3 months |
6 months |