Getting: deepgram connection closed unexpectedly #997
Replies: 1 comment
-
Realizing now that this log entry and the job_id are associated with Livekit. I believe this issue is on my side with an LLM function taking too long to finish. Will close and keep comment up for others. Will reopen if needed. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi,
We're receiving the following errors in our log. They are fairly consistent:
Exception: deepgram connection closed unexpectedly {"pid": 506, "job_id": "AJ_nz2WULao5S7e"}
Exception: deepgram connection closed unexpectedly {"pid": 755, "job_id": "AJ_ygTvhQ3cyVBo"}
These were about a week apart. At first we thought it was a random error, but we have lots of these in the log.
Can someone at deepgram inspect the job_id behind the scenes and give us a clue about what's wrong? Thanks in advance.
Beta Was this translation helpful? Give feedback.
All reactions