webhook showing 500, but the response was 200 with...
# support
here is another CallID: 71a2f67b-e5c7-4b1c-bc10-06793e9634d7 "error": "Your server rejected
assistant-request
webhook. Error: timeout of 7500ms exceeded", "assistantRequestError": "Your server rejected
assistant-request
webhook. Error: timeout of 7500ms exceeded", "assistantRequestResponse": { "error": "Your server rejected
assistant-request
webhook. Error: timeout of 7500ms exceeded" } https://cdn.discordapp.com/attachments/1389601827795767326/1389662854767972412/image.png?ex=68656fe3&is=68641e63&hm=afa8e7c818c0241604d4b49ec6951bf8d374cb66c03396096eec54da6e4e7555&
c
Hey Ron, thanks for the details. Our team will look into it and let you know soon.
r
many more examples not that it is easy to search your logs
message has been deleted
this is not promissing
No update?
c
Hi sorry for the delayed response, could you please provide the request payload you are sending in make to VAPI?
r
you can find it in the VAPI logs
this call id d2a3a8c7-1f41-43f9-a466-2263c9feeb2d Assistant Request shows 500 response then the next log Status Update shows the 200 response from the API
c
Hey Ron, I sincerely apologize for the delay in our responses this week. We experimented with some process adjustments that didn’t work as intended, and unfortunately, this caused some disruptions. That’s entirely my responsibility. Just a quick note—our team is unavailable on weekends. However, if something urgent or critical comes up, feel free to reach out to me directly, and I’ll assist you. The support issues will be resolved in the coming weeks, and starting Monday, you can expect more consistent and improved support. Thank you so much for your patience and for continuing to stick with us!
r
I just need a response to the 7500ms error
c
Basically, you will need to respond back with the assistant data within 7.5 seconds and it should solve this issue. If this is not helpful. Let me know we can get on a quick call and work on it.
r
this is not helpful, as my first example it was < 3sec
c
You are only calculating the time it takes to respond back, but there is latency to travel back to the Vapi side, which is taking some time. Ideally, you should respond back within 1.5s, and it should solve this issue.
r
even when I have VAPI hit my development PC i hear it say 7.5 sec error and the whole call was not 7.5 seconds. I am very familiar with latency, which is on the order of milliseconds not seconds. Where is the datacenter ?
c
The datacenter is in the US and if you increase the timeout to something like 15000, do you still get the same error? Increasing the timeout has helped some of our users in this scenario
c
Hey Ron, please give it a try and let us know if it works.
r
It's been like that for weeks
c
Hey Ron, we deployed a fix yesterday for an issue regarding server response times. Please try some calls and let us know if you are still experiencing this issue
m
@Ron
check this CallId de5b7baa-aba2-4dce-a497-2f8f9bad7beb
check this CallId de5b7baa-aba2-4dce-a497-2f8f9bad7beb
64977b48-0b4b-433c-9a27-3616468c09aa i see the 20 sec in the Status Update but in the assistant request it is 7.5
c
Hey Ron, sorry for the delayed response. Our database is not showing the call ids you provided and we would like to request some more recent call ids for further investigation of this issue. Also, please be sure to disable
async
on your tool for faster runtimes