20% of inbound calls having error with no call log...
# support
t
Depending on the day, 15-20% of our inbound calls are receiving error messages. We have an assistant-request hit our server, which responds with a custom assistant for each call. An example twilio call SID is
CAe188de692d456114f563a4a17cb07683
, and VAPI call ID
d414bd19-6c85-40bf-b984-ce52c68d18a0
. When visiting https://dashboard.vapi.ai/calls/d414bd19-6c85-40bf-b984-ce52c68d18a0 (which is not found in the call log), the page has an error:
r is undefined
. A screenshot is included. This call is not visible within the VAPI dashboard. The only information I have on this call existing is my server's log and the Twilio call log (Monitor => Logs => Calls). A screenshot is included of the Twilio webhook history The error said to the user is
Copy code
xml
<Response>
    <Say>Your server rejected `assistant-request` webhook. Error: timeout of 7500ms exceeded</Say>
</Response>
My server received the request for the assistant at 2025-04-09 00:31:56.021451+00, and the call ended at 2025-04-09 00:32:03.48915+00. https://cdn.discordapp.com/attachments/1359330912621563985/1359330913292517538/image.png?ex=67f71710&is=67f5c590&hm=e9632d80f244692a19a673977031ab32673f4b6d4bb66b8b36fa61e1271f1100& https://cdn.discordapp.com/attachments/1359330912621563985/1359330913665941674/image.png?ex=67f71710&is=67f5c590&hm=9b0cb5edd19787dabddb355bc9328e4f237d325cb030695ef58c42498b091044&
v
Hi there! 👋 I see you're experiencing issues with some of your inbound calls not being logged in VAPI. I'm unable to determine the exact cause of your specific issue without more detailed diagnostics. However, I can help you understand what might be happening and provide some troubleshooting steps. Based on the information you've provided, I can see several potential issues: ## The Timeout Issue The error message indicates that your server took too long to respond to the
assistant-request
webhook:
Copy code
Your server rejected `assistant-request` webhook. Error: timeout of 7500ms exceeded
According to the timestamps you provided, your server received the request at 00:31:56 and the call ended at 00:32:03, which is about 7 seconds later. This aligns with the 7500ms (7.5 seconds) timeout mentioned in the error message. According to [troubleshooting information](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1336345690393149452), this could be caused by: 1. **Server response time**: Your server might be taking too long to process the request and respond 2. **Network delays**: There might be network issues between VAPI and your server 3. **Server load**: Your server might be under heavy load, causing it to miss incoming webhook calls ## The "r is undefined" Error The "r is undefined" error you're seeing in the dashboard is likely related to the missing call logs. According to [error information](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1344328162024362095), this could be caused by: 1. **Outdated daily-js version**: The error might be related to using an outdated version of the daily-js library 2. **VAPI UI bugs**: The VAPI UI has known bugs that could be causing this error ## Troubleshooting Steps Here are some steps you can take to debug this issue: 1. **Check your server logs**: Look for any errors or slow response times in your server logs during the time of these failed calls
2. **Optimize your server response time**: Try to make your server respond faster to the
assistant-request
webhook. According to [webhook information](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1336345690393149452), you should aim to respond within the 7.5-second timeout period 3. **Check webhook delivery logs**: According to [debugging information](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1334280135683084328), you can access webhook delivery logs through the VAPI dashboard to see if there are any issues with webhook delivery 4. **Test your endpoint manually**: Try to trigger the webhook manually using a tool like Postman or cURL to verify that it's operational and can receive data as expected 5. **Simplify your response**: If your server is doing complex processing before responding, try simplifying it temporarily to see if that resolves the timeout issue 6. **Check network connectivity**: Ensure there are no network issues between VAPI and your server Is there anything specific about your server setup or the processing you're doing during the
assistant-request
webhook that might be causing delays? Sources: - [Reasons why inbound calls might not be logged in VAPI](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1332470088078590023) - [Causes of the
r is undefined
error in the VAPI dashboard](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1344328162024362095) - [Troubleshooting steps for
assistant-request
webhook timeouts in VAPI](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1336345690393149452) - [How to debug call logs in VAPI](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1334280135683084328)
t
There was a process that started at 2025-04-09 00:31:56.034+00 and ended at 2025-04-09 00:32:04.95744+00. How can I change the request timeout?
@Vapi Support Bot
v
Message marked as helpful by @taco! 🎉
v
Hi there! 👋 I see you're asking about changing the request timeout for the assistant-request webhook in VAPI. I can definitely help with that! Based on the information I found, there are several ways to increase the timeout setting: ## Option 1: Update the
timeoutSeconds
parameter You can use a PATCH request to update the
timeoutSeconds
parameter in your assistant configuration:
Copy code
bash
curl -X PATCH 'https://api.vapi.ai/assistant/{assistant_id}' \
-H 'Authorization: Bearer YOUR_API_KEY' \
-H 'Content-Type: application/json' \
-d '{
  "server": {
    "url": "https://your-server-url.com",
    "secret": "your-secret-key",
    "timeoutSeconds": 20,
    "headers": {
      "custom-header": "header-value"
    }
  }
}'
This would increase your timeout from the default 7.5 seconds to 20 seconds, which should accommodate your process that's taking around 8-9 seconds to complete. ## Option 2: Update via
analysisPlan.structuredDataRequestTimeoutSeconds
Alternatively, you can update the
analysisPlan.structuredDataRequestTimeoutSeconds
setting: 1. Go to the API documentation:
https://docs.vapi.ai/api-reference/assistants/update-assistant
2. Copy your private key from the dashboard:
profile > api keys > private api key
3. Make changes to the
analysisPlan
object, setting
structuredDataRequestTimeoutSeconds
to
20s
4. Make sure to include all previous values along with this new timeout value ## Option 3: Contact Vapi Support If you need specific adjustments or are having trouble with the API methods, you can contact Vapi support directly to discuss customization options for your specific use case. Would you like me to provide more details on any of these methods? Sources: - [How to change the request timeout for the assistant-request webhook in VAPI](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1341692740454584331)
- [How to change the request timeout for the assistant-request webhook in VAPI](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1265637856383078461) - [How to change the request timeout for the assistant-request webhook in VAPI](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1244742792580694097)
t
I need support then to change this. I don't use assistants My org ID is 06bcae9b-0274-4346-ae14-af1ab8fc1ed5
A call can ring for a long time, so 7.5s should not be the limit
k
Marking this ticket as Solved ✅