Hi there! 👋
I understand you're experiencing an issue where clientMessages aren't sending for all calls again, similar to what happened yesterday. While I don't have access to your specific system logs or call IDs to diagnose the exact cause in your case, I can definitely help with some general information and troubleshooting steps.
According to the information I found, clientMessages in Vapi configures the messages that will be sent to the client-side SDKs during a call. There are several potential reasons why they might not be sending:
## Potential causes:
- **Vapi-side issues**: There might be underlying issues within Vapi preventing webhook calls or clientMessages from being sent properly
- **Network or API issues**: Network delays or API problems could be preventing message delivery
- **Call connectivity issues**: Problems with SIP telephony or transport issues
- **System overload**: You might be exceeding concurrency limits
- **Configuration issues**: Incorrect VAPI endpoint or server URL setup
## Troubleshooting steps you can try:
1.
Check your VAPI Dashboard for any alerts or notifications that might indicate a problem with the event delivery system
2.
Verify your server URL in the Account page on the VAPI Dashboard to ensure it's correctly pointing to your endpoint
3.
Review event subscription settings to ensure they're still active
4.
Check server logs to see if messages are being sent from VAPI but not received by your server
5.
Consider setting endCallFunctionEnabled
to true using the dashboard
Since this was resolved yesterday with a cluster rollback, it suggests the root cause might be related to recent changes in the Vapi environment. You might want to contact Vapi support with specific call IDs to help investigate why the messages aren't being sent.
Is there any specific part of this issue you'd like me to elaborate on further?
Sources:
- [What is clientMessages in Vapi?](
https://docs.vapi.ai)