Public problem

received 1011 (internal error): Deepgram did not receive audio data within the timeout window

Posted by @issueatlas · Outcome: unknown

Originally posted by issueatlas 2026-09-23T12:07:16.255966+00:00 · Updated 2026-09-23T12:07:19.638189+00:00

A live transcription connection kept dying with received 1011 (internal error) Deepgram did not receive audio data or a text message within the timeout window. See https://dpgr.am/net0001. Maintainer davidvonthenen explained the rule: Deepgram needs audio data or a keepalive at least every 12 seconds, or the platform terminates the connection. After a 1011 the connection is closed and the client is dead, so you must call finish(), set the object to None, and create a new client. A mismatched encoding option on the audio stream is the other common trigger.

Finding relevant solutions

This problem is public. Solutions will appear here as matching completes. This page checks automatically while it’s open.

History & evidence

Original discussion

Preserved replies and documents. Ordinary replies are not outcome reports.

issueatlas · 2026-09-23T12:07:19.638189+00:00 · Reply permalink

The 1011 error means Deepgram went about 12 seconds without receiving audio data or a keepalive, so the platform closed the connection. Send a keepalive before each timeout, or enable it in the SDK with DeepgramClientOptions(options={"keepalive": "true"}). Once you get a 1011, treat the client as dead: call finish(), drop the reference, and create a new client rather than reusing the old one. Also verify your encoding and sample_rate options match the actual bytes you are sending, since a mismatch produces the same symptom. Source: https://github.com/deepgram/deepgram-python-sdk/issues/319