Cartesia TTS Error

I keep having these with my cartesia TTS and it messes up the conversation via the phone :

WARNING:livekit.agents:failed to synthesize speech: Request timed out., retrying in 2.0s
WARNING:livekit.agents:failed to synthesize speech: Request timed out., retrying in 2.0s
{“message”: “failed to synthesize speech: Request timed out., retrying in 2.0s”, “level”: “WARNING”, “name”: “livekit.agents”, “tts”: “livekit.agents.inference.tts.TTS”, “attempt”: 2, “streamed”: true, “pid”: 236, “job_id”: “AJ_aFfvMD3HReb3”, “room_id”: “RM_a7CG4SVxr5aV”, “timestamp”: “2026-05-26T16:32:38.387680+00:00”}

@Keynar, The “retrying in 2.0s” is the framework’s default retry:

You can raise the timeout with conn_options=APIConnectOptions(timeout=20) on the TTS, but for a phone call that masks rather than fixes. A 10s+ TTS latency already breaks the conversation. The real question is whether synthesis is genuinely slow (long segments, slower model) or intermittently degrading on Cartesia’s side.

Two quick checks: correlate your failure timestamps (log shows 2026-05-26T16:32 UTC) against Cartesia’s status page; if they had degradation in that window, it’s provider-side and transient. And check which Cartesia model you’re on, since the lowest-latency model is the safer choice for telephony.

For production telephony, the durable fix is a fallback TTS. The inference path supports it (there’s a tts-fallback test in the repo), so configure a secondary provider via FallbackAdapter [ docs.livekit.io/agents/logic/fallback-strategies ]. When Cartesia times out, it fails over to the backup instead of dead-airing the call, which is what’s currently messing up your conversations.

It’s unclear to me whether this is an occasional issue, or if the TTS just does not work. If it’s an occasional issue then please follow @Muhammad_Usman_Bashir 's reply above. If Cartesia TTS just does not work for you, please share your AgentSession configuration and reproduction steps. It’s also possibly related to this: Does cartesia/sonic-3-latest still route to Sonic 3.5, or Sonic 3? - #3 by darryncampbell