Sporadic 500/internal server error from flux-general-en

[ayazhafiz]

Hi folks. We're using the flux websocket API and are seeing infrequent (~4 in 1000) instances of 500s from flux during an active transcription session. Here is one example of such an error:

{"code":"INTERNAL_SERVER_ERROR","sequence_id":638,"description":"An internal server error occurred; please try again later","type":"Error"}

this is returned via the ListenV2FatalError message.

Here are a few request IDs that have experienced this:

c8ad94fa-9233-41ed-8b27-c3ca23d81943
a4312868-6618-4ded-8744-cd19dba40442
c2ffcfda-8b72-4758-99ce-ab405b5e6807
a35cc392-ab0e-4c5d-b8d5-1f8a5e914e9c

We are using the cloud API (api.deepgram.com/v2/listen) with the following query parameters:

model=flux-general-en
encoding=linear16
sample_rate=8000
eager_eot_threshold=0.65
keyterm=<word1>, ..., keyterm=<wordn>

Any help would be appreciated. Thanks!

[deepgram-community[bot]]

Thanks for asking your question. Please be sure to reply with as much detail as possible so the community can assist you efficiently.
_{Consider joining our Discord community for more opportunity to engage with your fellow Deepgram users. You can earn points which can be redeemed for cool stuff by being active in our communities!}

[deepgram-community[bot]]

Hey there! It looks like you haven't connected your GitHub account to your Deepgram account. You can do this at https://community.deepgram.com - being verified through this process will allow our team to help you in a much more streamlined fashion.

[deepgram-community[bot]]

It looks like we're missing some important information to help debug your issue. Would you mind providing us with the following details in a reply?

• The programming language you are working in (e.g. JavaScript, Python).

[ayazhafiz]

JavaScript

[deepgram-community[bot]]

hey, thank you for sharing all the details above. I was able to dig into the logs from those request IDs, and this appears to be the same as a recently discovered, rare timeout issue that we've got a fix being deployed soon for. I will follow up here when that change goes out.

This message was sent by nick kaimakis from Deepgram, via our community automation.

[ayazhafiz]

Thank you!