orchestrator
2023.4
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
- SmartCard Authentication
- Audit
- Settings - Tenant Level
- Resource Catalog Service
- Automation Suite robots
- Folders Context
- Automations
- Processes
- Jobs
- Triggers
- Logs
- Monitoring
- Queues
- Assets
- Storage Buckets
- Test Suite - Orchestrator
- Test Automation
- Testing Data Retention Policy
- Integrations
- Classic Robots
- Troubleshooting
Orchestrator User Guide
Last updated Oct 17, 2024
Testing Data Retention Policy
When you execute tests and use testing artifacts, it is recommended to be aware of their default data retention policies. Check out the table below to see the data retention periods for objects used for testing.
| Objects | Data retention period |
|---|---|
| Job information | The default period is 30 days, but you can configure it to be from 1 to 180 days.
|
| Robot logs | 30 days |
| Other testing artifacts (test results, assertions, assertion screenshots, activity coverage, attachments) | Indefinite |
