https://vapi.ai/ logo
Join Discord
Powered by
deepgram pipeline errors last 2 hours
# support
m
An error occurred in this call: pipeline-error-deepgram-returning-502-network-error Getting this error constantly. It just worked once in the last two hours. https://cdn.discordapp.com/attachments/1375242712898469959/1375242713653448795/image.png?ex=6830fa15&is=682fa895&hm=639964143ba0f2f39ff61ab6caec2eb30aa2b7ddebdc7d26f905286749887b6f&
@Vapi Support Bot
k
Hey! To help track down this issue, could you share: - The call ID This would really help us figure out what went wrong!
s
@Shubham Bajaj here is the call id
a6f16d1b-6953-402d-9ee6-78600e021cc9
75dbe2fa-26da-4365-9322-cc11e672856d
979925aa-c16f-4240-b69b-3c168290ad1e
v
Thank you for sharing the call IDs and error details. To help narrow down the cause of the repeated 
pipeline-error-deepgram-returning-502-network-error
, could you confirm if you have recently changed any network settings, API keys, or Deepgram configuration in your custom transcriber setup? This will help determine if the issue is related to configuration or provider connectivity. If not, please let us know if the issue persists across different environments or only in a specific deployment. Sources: - [Vapi Call Ended Reasons](https://docs.vapi.ai/calls/call-ended-reason) - [Vapi Custom Transcriber Guide](https://docs.vapi.ai/customization/custom-transcriber)
You're encountering repeated 
pipeline-error-deepgram-returning-502-network-error
issues, which indicate network or service disruptions between Vapi and Deepgram. The best next step is to email [support@vapi.ai](support@vapi.ai) with your call ID (
a6f16d1b-6953-402d-9ee6-78600e021cc9
) and a description of the issue. This will allow the Vapi team to investigate the root cause and coordinate with Deepgram if needed. Persistent 502 errors are often outside your direct control and require provider-side investigation. Sources: - [Vapi Call Ended Reasons](https://docs.vapi.ai/calls/call-ended-reason) - [Vapi Support](https://docs.vapi.ai/support)
Thank you for sharing the error details. To help us investigate the repeated 
pipeline-error-deepgram-returning-502-network-error
, could you please confirm if you are using your own Deepgram API key or the default Vapi integration? This will help us narrow down whether the issue is related to your custom setup or the provider service itself. If possible, please also mention if you have made any recent changes to your Deepgram configuration or network environment. For persistent issues, you may also want to contact [Vapi support](https://docs.vapi.ai/support) with your call ID and account email for a deeper investigation. Source: - [Vapi Call Ended Reasons](https://docs.vapi.ai/calls/call-ended-reason)
Action Required: Since you are experiencing repeated 
pipeline-error-deepgram-returning-502-network-error
issues, please email [support@vapi.ai](support@vapi.ai) with your call IDs (e.g., 
a6f16d1b-6953-402d-9ee6-78600e021cc9
, 
75dbe2fa-26da-4365-9322-cc11e672856d
, 
979925aa-c16f-4240-b69b-3c168290ad1e
) and your account email. This will allow the Vapi team to investigate the Deepgram pipeline errors in detail and provide targeted assistance. For persistent provider/network errors, escalation to support is the recommended next step. Reference: [Vapi Call Ended Reasons Documentation](https://docs.vapi.ai/calls/call-ended-reason) Sources: - [Vapi Call Ended Reasons Documentation](https://docs.vapi.ai/calls/call-ended-reason) - [Vapi Support](https://docs.vapi.ai/support)
k
They are facing degradation.
m
We still see the same issue even though their status page says the the incifdent has been resolved.
v
It looks like the 
pipeline-error-deepgram-returning-502-network-error
is still persisting for you, even though Deepgram's status page now shows the incident as resolved. This can definitely be frustrating, especially when the issue appears to be outside your direct control. If you haven't made any recent changes to your configuration or network, it's possible that there are still lingering effects from the earlier service degradation. You're not alone in experiencing this, and your detailed call IDs and updates are helpful for tracking the situation. If anything changes or you notice improvements, feel free to share an update!
Since the 
pipeline-error-deepgram-returning-502-network-error
persists even after Deepgram's status page shows the incident as resolved, the best next step is to escalate to Vapi support. Please email [support@vapi.ai](support@vapi.ai) with your call IDs and a description of the ongoing issue. This will allow the Vapi team to coordinate with Deepgram and investigate further on your behalf. Reference: [Vapi Call Ended Reasons](https://docs.vapi.ai/calls/call-ended-reason), [Vapi Support](https://docs.vapi.ai/support) Sources: - [Vapi Call Ended Reasons](https://docs.vapi.ai/calls/call-ended-reason) - [Vapi Support](https://docs.vapi.ai/support)
m
d80acbfb-0723-452f-80ad-e6efbb724b97 eafb5c41-8048-486c-b09d-31caedf33a36 a6f16d1b-6953-402d-9ee6-78600e021cc9
s
@Shubham Bajaj
v
Thank you for sharing the additional call IDs and keeping us updated on the situation. It's understandable that this ongoing error is frustrating, especially when the status page suggests the incident is resolved but the issue persists on your end. Your detailed updates are very helpful for tracking and understanding the scope of the problem. If you notice any changes or patterns, feel free to share them—every bit of information can help in identifying the root cause.
It sounds like the 
pipeline-error-deepgram-returning-502-network-error
is still affecting your calls, even though Deepgram's status page now shows the incident as resolved. This kind of lingering issue can definitely be frustrating, especially when it seems to be outside your direct control. Your detailed updates and call IDs are valuable for tracking the situation. If you notice any changes or improvements, sharing those observations can help with ongoing monitoring. You're not alone in experiencing this, and your persistence in reporting the issue is appreciated.
Next Step: Please email support@vapi.ai with your call IDs and a brief description of the ongoing 
pipeline-error-deepgram-returning-502-network-error
. This will allow the Vapi team to coordinate with Deepgram and investigate the issue further on your behalf. Persistent 502 errors are typically provider-side and require escalation for resolution. [Reference: Vapi Call Ended Reasons](https://docs.vapi.ai/calls/call-ended-reason) Sources: - [Vapi Call Ended Reasons](https://docs.vapi.ai/calls/call-ended-reason) - [Vapi Support](https://docs.vapi.ai/support)
k
Can you try again?
PreviousNext
Powered by