quota_exceeded
quota_exceeded
Section titled “quota_exceeded”HTTP status: 429 Too Many Requests
How to fix
Section titled “How to fix”- Slow down and retry with exponential backoff. Start at 1 second, double on each retry, cap at 60 seconds. Most transient bursts clear within a minute.
- Check your current usage. Open Billing → Usage in the dashboard to see the per-day / per-month counter against your plan's cap.
- Upgrade the plan if you're consistently bumping the ceiling. Settings → Billing → Change plan.
- Contact support if you need a temporary lift for a one-off backfill — we can raise the cap manually.
What this means
Section titled “What this means”You hit either a request-rate gate (too many requests per second from one org) or a monthly quota gate (your plan's job-count or storage allowance is full). The API gateway returns 429 in both cases; the distinction is in our logs against your request_id.
Related errors
Section titled “Related errors”plan_required— feature exists but your tier doesn't include itpayment_required— billing is past due, all writes are blocked
Still stuck?
Section titled “Still stuck?”Contact support with your request_id (looks like req_01HF3JKB...). We'll tell you which gate fired and how far over you are.