Call.in progress.error vapifault deepgram transcri...
# support
m
Hi, Starting today I got a bunch of these errors. I am seeing "Deepgram Flux WebSocket error" "Unexpected server response: 429" in the call logs. There was almost no activity today so I do not know why it would be giving a too many requests error. The call is never allowed to start. I did notice that the transcriber was set to flux general english. When I set it to Nova 3 I didn't notice the problem anymore. Some CallIds: 019d078b-f8b5-788c-b95d-6b722cbdb7bd, 019d081d-611a-777e-baf2-08017bb45b20, 019d078c-473e-733a-b662-cd9ec0fdbffa There are a bunch more Please advise Thanks!
v
To prevent call failures when the Deepgram Flux transcriber encounters errors, configure a fallback transcriber in your assistant's settings. Here’s an example of how to set this up via API:
Copy code
json
{
  "transcriber": {
    "provider": "deepgram",
    "model": "flux-general-en",
    "language": "en",
    "fallbackPlan": {
      "transcribers": [
        { "provider": "deepgram", "model": "nova-3", "language": "en" },
        { "provider": "azure", "language": "en-US" }
      ]
    }
  }
}
This ensures your calls continue seamlessly if the primary transcriber fails. For more details, see the [transcriber fallback documentation](https://docs.vapi.ai/customization/transcriber-fallback-plan). Source: - [Transcriber fallback configuration](https://docs.vapi.ai/customization/transcriber-fallback-plan)
m
Ok, thanks. What about the ElevenLabs message error?
v
Message marked as helpful by @Michael! 🎉
c
Hi, Sorry for the inconvenience caused. There was an an outage on Vapi’s end, which is resolved now. For more details and updates, please refer to: [https://status.vapi.ai/incident/853120](https://status.vapi.ai/incident/853120) Thank you & have a lovely day! Best regards, Oshi Raghav Customer Support Team | Vapi