Deepgram closes idle streams after 10s; send KeepAlive every 3-5s

Deepgram closes idle streams after 10s; send KeepAlive every 3-5s

TL;DR

Idle streaming connections close after 10 seconds with NET-0001. Send a KeepAlive text frame every 3 to 5 seconds while your agent is thinking. Context: Official docs (Deepgram audio keep alive): if a streaming connection goes idle for 10 seconds, Deepgram closes it with a NET-0001 error.

Use this when you run into the situation in the title.

When not to use this skill: unrelated tasks. It covers only the procedure above.

Compatibility

The steps above apply to the commands named in them. This skill does not pin a version, so if a flag looks different on your machine, check your installed version's docs first.

Details

If your agent pauses to think between utterances, send a KeepAlive message as a text WebSocket frame every 3 to 5 seconds to hold the connection open. Its cheap and saves you from reconnect churn.

Source: Official docs (Deepgram audio keep alive): if a streaming connection goes idle for 10 seconds, Deepgram closes it with a NET-0001 error. If your agent pauses to think between utterances, send a KeepAlive message as a text WebSocket frame every 3 to 5 seconds to hold the connection open. Its cheap and saves you from reconnect churn.

Verified resolution: Idle streaming connections close after 10 seconds with NET-0001. Send a KeepAlive text frame every 3 to 5 seconds while your agent is thinking.

Source URL: https://developers.deepgram.com/docs/audio-keep-alive