Calls stucked in status 'queued'
# supportj
jorgemtzvega
03/26/2025, 6:43 PMI have a lot of calls stucked in status "queued" with "unknown" in the dashboard logs.
some examples:
adf35155-9115-4fd1-9550-9def4003c2b4
cfd3e059-631a-4c6d-b470-1cc1000546fc
6b9505c9-eb8d-4122-82e5-91beaf9cc903 @User
v
Vapi Support Bot
03/26/2025, 6:45 PMHi there! 👋 I see you're having trouble with calls stuck in the "queued" status.
I'm unable to determine the exact cause of your specific calls being stuck without examining your account configuration. However, I can definitely help with some common causes and troubleshooting steps for this issue.
Based on the information I found, here are some possible causes for calls stuck in the "queued" status:
1. Concurrency Limit Issues - You might be reaching your concurrency limit, which prevents new calls from being processed. According to [information from Discord discussions](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1336054616206348479), this can cause calls to remain in the queue.
2. SIP Connection Problems - There might be issues with SIP connections preventing calls from connecting properly. The system might be repeatedly sending INVITE requests for SIP call setup but not receiving proper responses.
3. Twilio Connectivity Issues - If the initial connection between Twilio and Vapi fails, calls might not transition out of the "queued" state.
4. Configuration Issues - Incorrect VAPI configuration settings can affect call setup and response times, potentially leading to calls getting stuck.
As for the "unknown" status in your dashboard logs, this could indicate:
- Twilio number misconfiguration
- No assistant being associated with the phone number
- The call being rejected inbound
- A system outage affecting status reporting
Here are some troubleshooting steps you can take:
1. Check for Concurrency Limits - If you're making a high volume of outbound calls, consider increasing your concurrency limit.
2. Review VAPI Configuration - Check settings that might affect call setup and response times, such as
silenceTimeoutSecondsresponseDelaySecondsllmRequestDelaySecondsVapi Support Bot
03/26/2025, 6:45 PM3. Check SIP Configuration - Ensure that the SIP URI is correctly formatted and that your network allows traffic on the SIP protocol.
4. Contact VAPI Support - For in-depth investigation, reach out to VAPI support at [support@vapi.ai](support@vapi.ai) with your call IDs and details about the problems.
5. Try a Test Call - Use Vapi's free telephony for verification to see if the issue persists.
Is there any specific part of this issue you'd like me to elaborate on further?
Sources:
- [Discord discussion about concurrency limits](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1336054616206348479)
- [Discord discussion about SIP connection issues](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1334111884315725845)
- [Discord discussion about Twilio connectivity](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1336407849806462976)
- [Discord discussion about configuration issues](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1332286268805087272)
- [Discord discussion about unknown status](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1332470088078590023)
- [Discord discussion about contacting support](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1333747605628391434)
Vapi Support Bot
03/26/2025, 6:46 PMHi there! 👋 I see you're experiencing issues with calls stuck in the "queued" status.
I'm unable to determine the exact cause of your specific calls being stuck without examining your account configuration in detail. However, I can help with common causes and troubleshooting steps for this issue based on information I've found.
Based on my research, here are some possible causes for calls stuck in the "queued" status:
1. Concurrency Limit Issues - You might be reaching your concurrency limit, which prevents new calls from being processed. According to [information from Discord discussions](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1336054616206348479), this can cause calls to remain in the queue.
2. SIP Connection Problems - There might be issues with SIP connections preventing calls from connecting properly. The system might be repeatedly sending INVITE requests for SIP call setup but not receiving proper responses.
3. Twilio Connectivity Issues - If the initial connection between Twilio and Vapi fails, calls might not transition out of the "queued" state according to [this discussion](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1336407849806462976).
4. Configuration Issues - Incorrect VAPI configuration settings can affect call setup and response times, potentially leading to calls getting stuck.
As for the "unknown" status in your dashboard logs, [information suggests](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1332470088078590023) this could indicate:
- Twilio number misconfiguration
- No assistant being associated with the phone number
- The call being rejected inbound
- A system outage affecting status reporting
Here are some troubleshooting steps you can take:
1. Check for Concurrency Limits - If you're making a high volume of outbound calls, consider increasing your concurrency limit.
Vapi Support Bot
03/26/2025, 6:46 PM2. Review VAPI Configuration - Check settings that might affect call setup and response times, such as
silenceTimeoutSecondsresponseDelaySecondsllmRequestDelaySecondsVapi Support Bot
03/26/2025, 6:47 PMHi there! 👋 I see you're experiencing issues with calls stuck in the "queued" status with "unknown" in the dashboard logs.
I'm unable to determine the exact cause of your specific calls without examining your account configuration in detail. However, I can help with common causes and troubleshooting steps for this issue based on information I've found.
Based on my research, here are some possible causes for calls stuck in the "queued" status:
1. Concurrency Limit Issues - You might be reaching your concurrency limit, which prevents new calls from being processed. According to [information from Discord discussions](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1336054616206348479), this can cause calls to remain in the queue.
2. SIP Connection Problems - There might be issues with SIP connections preventing calls from connecting properly. The system might be repeatedly sending INVITE requests for SIP call setup but not receiving proper responses, as mentioned in [this discussion](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1334111884315725845).
3. Twilio Connectivity Issues - If the initial connection between Twilio and Vapi fails, calls might not transition out of the "queued" state according to [this source](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1336407849806462976).
4. Transport Connection Failures - Some logs show calls waiting but "transport never connected" which could be related to your issue, as noted in [this discussion](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1342542851795324948).
As for the "unknown" status in your dashboard logs, [information suggests](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1332470088078590023) this could indicate:
- Twilio number misconfiguration
- No assistant being associated with the phone number
- The call being rejected inbound
Vapi Support Bot
03/26/2025, 6:47 PM- A system outage affecting status reporting
Here are some troubleshooting steps you can take:
1. Check for Concurrency Limits - If you're making a high volume of outbound calls, consider increasing your concurrency limit.
2. Review VAPI Configuration - Check settings that might affect call setup and response times, such as
silenceTimeoutSecondsresponseDelaySecondsllmRequestDelaySecondsVapi Support Bot
03/26/2025, 6:47 PMI've escalated your issue to our support team for further investigation. 🙌
Since this problem requires a direct examination of your account configuration to determine the exact cause, a human agent will need to look into your specific setup. The call IDs you've provided (adf35155-9115-4fd1-9550-9def4003c2b4, cfd3e059-631a-4c6d-b470-1cc1000546fc, 6b9505c9-eb8d-4122-82e5-91beaf9cc903) will help them investigate the root cause.
A support team member will reach out to you shortly to help resolve these calls stuck in the "queued" status. In the meantime, if you discover any additional information about the issue or have any other questions, please feel free to share them.
Thank you for your patience while we work to resolve this issue!
v
Vapi Support Bot
03/26/2025, 6:49 PMMessage marked as helpful by @jorgemtzvega! 🎉
k
Kyle Brunker
03/27/2025, 12:49 AMThere was a small issue on our end where our admin workers couldn't update the call status in real-time, and it took them a longer period of time to update the status. That's why you have in the dashboard, the call status is still to be queued or there is no status at all. Do a hard refresh, and then see you will find out the status for all of these calls. Let me know how it goes for you?
j
jorgemtzvega
03/27/2025, 12:37 PM@User Thanks for your help! I can see the updated status now. 🙌
k
Kyle Brunker
03/29/2025, 1:25 PMMarking this ticket as Solved ✅
2 Views