Limits & Quotas
Limits & quotas
Platform limits.
Overview
Platform limits for API rate, uploads, concurrent runs, and data retention. Exceeding limits returns 429 (API), upload rejection (Console), or queued runs (execution).
Enterprise plans include custom quotas negotiated in your account agreement. Standard limits documented here apply unless your contract specifies otherwise.
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
Assess usage
Review API rate headers in integration logs.
Monitor Operate → Runs for queued execution during peak windows.
Request increase
Contact support with organization ID, use case, and expected peak load.
Allow lead time for enterprise quota provisioning.
Key concepts
- API rate limits
- Per-organization request quotas with standard rate limit headers. See API rate limits documentation for retry guidance.
- Upload limits
- Requirements uploads typically limited to 10MB with supported MIME types enforced at upload time.
- Concurrent runs
- Concurrent validation limits vary by plan and agent fleet capacity. Contact support for enterprise quota increases.
- Data retention
- Run artifacts and logs retained per organization policy. Configure retention in Admin Center where available.
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?
