ElevenLabs Voice Design 409: wait and retry, or new key on Sume?
Voice Design now returns 409 while a preview generation is in progress; ElevenLabs says retry. On Sume, reuse an Idempotency-Key only for the same payload.

ElevenLabs Voice Design now returns 409 when a generation for the preview is already in progress, and its changelog says to retry the request after receiving it. That is a wait-and-retry signal. Sume's retry rules are a different shape: reuse an Idempotency-Key only for the same operation and payload, and use a new one to retry a failed Format run.
The ElevenLabs note is from its changelog; the Sume rules are from Jobs and results and Errors and credits, read 2026-10-01.
Which ElevenLabs calls return the 409?
The changelog lists Create voice from preview, Create voice previews, Design a voice and Remix a voice. The 409 means a generation for the preview is already in progress.
What does a 409 mean on Sume?
Sume's documented 409 codes are about job state: job_not_completed, job_not_cancelable or job_generation_already_started. The docs do not describe a 409 for "same work already running". Treat each code by name instead of retrying blindly.
| Signal | What the source says to do |
|---|---|
ElevenLabs 409 (preview in progress) | Retry the request |
Sume 429 | Back off; use retry-after when present |
| Sume replay of the same create | Reuse the same key only for the same operation and payload |
| Sume failed Format run | Retry with a new Idempotency-Key; the old one is bound to your receipt |
How do I write the retry loop?
Keep one idempotency key per logical create. If you get a network error or a timeout, resubmit with the same key and body and Sume returns the existing job instead of a second paid one. If a Format run ended in an error status, mint a new key, or prefer continuing the run so the clips already made are kept. Do not retry unsafe submits without a key at all.
Does the same pattern apply to previews on Sume?
If you already hold a Sume job id, poll that job rather than starting another. See retrying a failed run for the full rule.
Sources
Related posts
More in Developers
- Signing the EU transparency Code of Practice after 27 July 2026
The Commission says you can still sign the AI-content transparency code after 27 July 2026; that date only set the initial list. Which section fits an API team?
- Facebook Reels API: 30 posts per 24 hours, Instagram allows 100
Meta's Reels Publishing API allows 30 API-published posts in a 24-hour moving period, enforced on video_reels. Here is how to split a 100-item Sume queue.
- Facebook Reels error 1363127: resolution below 540x960
Error 1363127 means the Reels video is under the 540 x 960 minimum. Facebook recommends 1080 x 1920; in Sume use the 720p or 1080p tier in 9:16, not 360p.
- Facebook Reels error 1363129: frame rate must be 24 to 60 fps
Error 1363129 means the average frame rate is outside 24-60 fps. Conform the file to a fixed 24, 25, 30 or 60 fps with Sume Video Trim or Timeline, then retry.
Written by Sume