Sume 409 errors: job_not_completed, job_not_cancelable and more
A Sume 409 means the job operation does not fit the job's current status: job_not_completed, job_not_cancelable or job_generation_already_started.
A 409 means the requested job operation is not valid for the current status. The documented codes are job_not_completed, job_not_cancelable and job_generation_already_started (read 2026-10-06 in the errors docs).
What should my client do?
Read the job status first. Fetch results only from a completed job, and cancel only before generation starts.
What should I do in practice?
The status vocabulary is on the same page.
- Poll until terminal before reading results.
- Do not retry a 409 blindly.
- Cancel queued jobs early.
Sources
Related posts
More in Developers
- Sume 413 payload_too_large and 415: shrink the body, send JSON
413 means the request body is over the API limit. 415 means the body was not application/json, shown in details.received_content_type.
- Sume 429 rate_limited: honor retry-after and use an Idempotency-Key
On a Sume 429 rate_limited, back off using retry-after if present, and never retry an unsafe submit without an Idempotency-Key. Headers explained.
- A 5xx on a Sume paid submit never proves no job: retry with the key
On Sume, only a validation, authorization or balance error proves a paid create was refused. A 5xx does not, so retry with the same Idempotency-Key.
- sume/auto 400 unsupported_capability: 11 s, 2 s, 480p and silent audio
sume/auto fails closed on 2 s, 11 s, 480p, 768p and generate_audio false. The request is rejected before any provider call. Here is what to send instead.
Written by Sume