Limits & Quotas
Data retention
Overview
Run logs, artifacts, and reports are retained per organization policy. Defaults suit operational troubleshooting; extend retention for regulated industries via enterprise configuration.
Who should read this
- QA engineers, SREs, platform teams, and developers operating Zof Console and APIs.
When to use this workflow
- Onboarding new team members to Zof terminology and workflows
- Authoring internal runbooks aligned with Console labels
- Designing CI/CD or webhook integrations against documented behavior
Step-by-step procedure
Review policy
Admin Center → Platform → Data retention settings.
Document internal alignment with legal hold procedures.
Export before expiry
Operate → Reports and run artifacts → export to corporate storage for long-term archive.
Key concepts
- Default retention
- 90 days for run artifacts on standard plans unless otherwise specified in agreement.
- Legal hold
- Enterprise process to suspend deletion for litigation or audit; contact support.
Best practices
- Validate changes in staging before applying release gates to production.
- Include run IDs and timestamps when escalating issues to support or auditors.
- Align internal runbook terminology with Zof Console UI labels for clarity.
Was this page helpful?
