An ElevenLabs voice or model you relied on stopped working
Recent tracked changes that can explain it:
- •Limits the number of files held in memory for widget file-input, requiring summarization for larger sets.2026-08-03source
- •Removes existing audio filtering capabilities from ElevenAgents configuration, potentially breaking workflows relying on these filters.2026-08-03source
- •Breaking change for API clients requiring schema updates to include conversation_id in WebRTC token responses.2026-07-27source
- •Shorter default fallback window for the backup LLM cascade in ConvAI agents; remains user-configurable within the 2–15s range.2026-07-20source
What’s going on
Two model IDs account for most ElevenLabs breakage: eleven_monolingual_v1 and eleven_multilingual_v1, both deprecated and scheduled for removal on July 9, 2026, with the scribe_v1 transcription model on the same cutoff. The mechanism behind them is a rolling generation cycle — as newer models mature, older ones are marked deprecated and given a hard removal date, after which any call pinned to that ID either errors out or silently falls back to a different model that can sound noticeably different. Eleven v3 left alpha and became generally available in February 2026, so it's the TTS generation you're expected to move onto. Confirming a genuine retirement takes one look: open the changelog and check the exact model_id your integration sends — if it appears there with a stated removal date, the tool is ending support, not misbehaving. A voice that merely sounds a little off while its model sits on no deprecation list points elsewhere — a re-render, a stability/similarity setting, or an account change. The response is a migration: repoint pinned model IDs to the current generation (v3 for TTS, scribe_v2 or scribe_v2_realtime for transcription), re-audition each affected voice against the new model to pick the closest match, and re-render any assets built on a deprecated voice before the July 9 cutoff so nothing catches you mid-project. One production user described pinning eleven_multilingual_v1, then having to re-validate every voice once a removal date appeared — that's the pattern to plan around. Keep watching the changelog, because removal dates can shift and new deprecations arrive on their own schedule; note too that unrelated developer-facing changes, like the InteractionBudget enum dropping its async option, can break configs independently of any voice.
ElevenLabs has shown frequent recent tightening, mainly in model availability.
Frequent recent tightening — high constraint volatility right now.
Related problems