TTS audio generation stops when sending a second text with continue_=True on the same context

TL;DR

Pass continue\_=True on every context.send(), including the first chunk, and the audio generates sequentially across chunks.

Steps

1. Sending a second text chunk to the same TTS websocket context with continue_=True immediately stopped the ongoing audio generation instead of continuing sequentially. The docs on contexts did not make the pattern obvious. Another user found the fix: pass continue_=True on every context.send() call, including the very first chunk, not just the follow-ups. The reporter confirmed this resolved it.
2. What actually fixes it (verified in the thread):
3. When the second chunk kills the first chunk's audio, you are probably only setting continue_=True on the follow-up sends. Pass continue_=True on every context.send(), including the first chunk, and the audio generates sequentially across chunks. Check the Cartesia docs page on TTS websocket contexts for the full pattern. The reporter confirmed this fixed it after a user pointed out the first-chunk detail.

When to use

You are seeing this: The docs on contexts did not make the pattern obvious. Use this skill when you run into "TTS audio generation stops when sending a second text with continue_=True on the same context".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Someone asked: Sending a second text chunk to the same TTS websocket context with continue_=True immediately stopped the ongoing audio generation instead of continuing sequentially. The docs on contexts did not make the pattern obvious. Another user found the fix: pass continue_=True on every context.send() call, including the very first chunk, not just the follow-ups. The reporter confirmed this resolved it. The verified answer: When the second chunk kills the first chunk's audio, you are probably only setting continue_=True on the follow-up sends. Pass continue_=True on every context.send(), including the first chunk, and the audio generates sequentially across chunks. Check the Cartesia docs page on TTS websocket contexts for the full pattern. The reporter confirmed this fixed it after a user pointed out the first-chunk detail. Full thread: https://vectle.com/threads/thr_m9FVrTXfogtLBuE8upR7DA