Sume 503 provider_capacity_exceeded: retry later, same key
provider_capacity_exceeded means Sume's provider dispatch queue is full. Retry later with the same Idempotency-Key. provider_not_configured is different.
provider_capacity_exceeded means Sume's provider dispatch queue is full before the provider work was accepted. Retry later with the same idempotency key (read 2026-10-06 in the errors docs).
How is it different from provider_not_configured?
provider_not_configured means provider execution is not available in this runtime; do not retry aggressively, examine the catalog and runtime status instead.
What should I do in practice?
Quote the request id in a support message.
- Both are 503 responses.
- Retry capacity errors with backoff.
- Do not retry not-configured errors in a loop.
Sources
Related posts
More in Developers
- Sume has two 429s: rate_limited and queue_full, handled differently
rate_limited is a request window. queue_full means workspace concurrency and queue capacity are both full; wait for a job to finish or cancel one.
- Which statuses to retry when reading back a Sume job (Python)
After a Sume submit returns a job id, retry reads on 408, 425, 429, 500, 502, 503, 504 and 520 to 525. A tested Python classifier and the 409 gotcha.
- Webhook URL with user:pass@ gets a 400: verify the signature instead
Sume refuses a run webhook_url that carries credentials, plain HTTP or a private host. Authenticate your receiver with the signed headers, not the URL.
- Sume SDK 402 insufficient credits: it is returned, not thrown
Generated Sume SDK calls resolve with data, error and response. Turn a 402 into SumeInsufficientCreditsError with toSumeApiError and stop retrying.
Written by Sume