orchestrator
latest
false
- Getting started
- Best practices
- 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
- Cloud robots
- Folders Context
- Automations
- Processes
- Jobs
- Apps
- Triggers
- Logs
- Monitoring
- Queues
- Assets
- Business Rules
- Storage Buckets
- MCP Servers
- Indexes
- Orchestrator testing
- Resource Catalog Service
- Integrations
- Troubleshooting

Orchestrator user guide
Last updated Sep 17, 2025
Time-to-live Periods
linkTime 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
linkData expires once it exceeds the TTL period as follows:
Data Type |
Community |
Enterprise |
---|---|---|
Disconnected and unresponsive unattended sessions |
3 months |
6 months |