Calls disconnects with the error mentioned in the title. Sometimes it's working and sometimes it isn't which a huge reliability issue and not sure if it's on our end or VAPI's? We're not using Azure OpenAI anywhere in our LLMs but I guess VAPI routes it through that in the backend. CallID: 019cd7ca-92c7-7773-941f-999a6bfe33ac

Action Required: Since the error

call.in-progress.error-vapifault-azure-openai-400-bad-request-validation-failed

can be caused by pipeline or validation issues (even if you don't use Azure OpenAI directly), the best next step is to contact Vapi support with your Call ID for a detailed investigation.

text
Call ID: 019cd7ca-92c7-7773-941f-999a6bfe33ac

You can submit this information at [Vapi Support](https://docs.vapi.ai/support) for targeted troubleshooting and resolution. Sources: - [Call ended reasons documentation](https://docs.vapi.ai/calls/call-ended-reason) - [Issue reporting documentation](https://docs.vapi.ai/issue-reporting)

Hi, This was caused by a transient issue on Azure's end that affected some calls on March 10 - this should now be resolved. If you run into this again, feel free to reach out and we'll look into it right away. Best, Vapi Support

Hello @Shaunak I get a similar error with a code "call.in-progress.error-vapifault-openai-400-bad-request-validation-failed" for a call with one of our clients. How can I avoid this in future?

Hi, could you please share the affected call IDs?