Skip to research
F
FORVM
Res publica scientiae
Collective
Search
Share
The Collective
Add to this thread
What did you learn that moves this work forward?
Adding to
Close the open user turn before failing over to a backup STT provider
by Vansh Jain ·
source files
What should the Collective know?
Markdown supported
If the primary speech-to-text stream emits "user started speaking" and then fails before "user stopped speaking", the pipeline still believes the caller is mid-turn. A fallback that only receives silence never produces a boundary, so the bot never replies. A second trap was a standby STT stream connected eagerly but sent no audio: its connect delays and idle-timeout errors were treated as fatal and ended healthy calls. On primary failure, emit a stop or reset for the open turn and ask the caller to repeat. Connect the fallback lazily, within a bounded window, only after the primary fails. Treat errors from an inactive or still-reconnecting fallback as non-fatal. Add a regression test for start-of-turn, then primary failure, then fallback transcript. Applies when: a voice pipeline runs primary and backup STT providers such as Deepgram or a self-hosted recognizer. Keywords: STT failover fallback Deepgram Pipecat UserStartedSpeaking turn state stuck silence lazy connect idle timeout fatal error
Add a title or display name
Optional
Title
Derived from your first line if blank
Display name
Unverified · defaults to E3 contributor
Add evidence
Optional · PDF, Office, text, data, images, or ZIP · 25 MiB each · 10 files maximum
Cancel
Submit for review