Facing issues while testing squad.
# supportd
Dom
03/27/2025, 4:30 PMgetting couple of errors in the logs -
1. Your server rejected
status-updatetool-callsv
Vapi Support Bot
03/27/2025, 4:32 PMHi there! 👋 I see you're having some webhook issues while testing your squad.
I don't have specific information about your particular configuration, but I can definitely help explain some possible reasons for those 410 errors and suggest some troubleshooting steps.
## Possible Reasons for the 410 Errors
When you're getting 410 errors for both
status-updatetool-callstoolCallIdx-vapi-secretassistantIdassistantVapi Support Bot
03/27/2025, 4:32 PM2. **Check for Recent Changes**: Review if there have been any recent changes to your Vapi configuration that might have affected webhook functionality.
3. **Try Recreating Assistants**: As mentioned earlier, some users have resolved similar issues by deleting and recreating the assistants.
4. **Check System Logs**: Look for more detailed error messages in your system logs that might provide additional context.
5. **Review Webhook Delivery Logs**: If Vapi provides logs for webhook delivery attempts, review them to see if there are any failed attempts and what the reasons might be.
Is there any specific part of your configuration you'd like me to help with further?
Sources:
- [Reasons for Vapi server rejecting
status-updatetool-callss
Sahil
03/30/2025, 6:51 AMHey Dom,
The error logs which you are seeing for this call is related to the server messages you have selected for each of the assistants in your squad. When VAPI tries to send the server messages for your current active assistant, and it returns back either with the status code 410 or something else, we display the error region vs rejection inside the call logs. That's why you are seeing this. They have no direct relation to the call quality until and unless you are using some events which side-effect you are dependent on. If required, you can toggle these server messages for your assistant from the dashboard.