stormy-gold•5h ago
concurrency level reached id: a1cdb192-59a5-4f97-8baa-d528d7f9397a
i have purchased 100 more call lines and i still get an email that i have reached my concurrency level. when i creat my outbound campaign to call 100 contacts is will say that it is scheduled while i clicked the option to call now. Please solve this as soon as possible as i am loosing clients because of this.
9 Replies
Thank you for sharing the details.
To help resolve your issue quickly:
Could you please confirm if your Vapi organization’s concurrency limit (as shown in the Vapi Dashboard > Billing Settings) has been updated to reflect your recent purchase, or does it still show the previous limit? This will help determine if the new call lines are active on the Vapi side or if further action is needed. Source: - Outbound campaigns overview
Could you please confirm if your Vapi organization’s concurrency limit (as shown in the Vapi Dashboard > Billing Settings) has been updated to reflect your recent purchase, or does it still show the previous limit? This will help determine if the new call lines are active on the Vapi side or if further action is needed. Source: - Outbound campaigns overview
⤵️ Mention @Vapi Support Bot for follow-ups 🐥
stormy-goldOP•5h ago
stormy-goldOP•5h ago
@Duckie
Thank you for confirming your reserved concurrency is set to 100. To help narrow down the cause, could you please check if your outbound campaign dashboard shows any queued or failed calls, and if so, what status or error message is displayed for those calls?
Source:
- Outbound campaigns overview
stormy-goldOP•5h ago
this appears and i get a an email saying that my concurecy limit has been reached
stormy-goldOP•4h ago
@Duckie
Action Step:
Please try logging out and back into your Vapi Dashboard, then navigate to Billing Settings and verify that your concurrency limit is reflected as 100. If it is, but your campaign is still queued or you receive concurrency limit emails, open a support ticket with Vapi and include your organization ID, campaign ID, and screenshots of your concurrency settings and error messages. This will help the support team quickly investigate and resolve any backend provisioning issues. Tip: You can also check the Subscription schema to confirm your concurrency limits as seen by the system. Sources: - Outbound campaigns overview - Changelog November 11, 2024
Please try logging out and back into your Vapi Dashboard, then navigate to Billing Settings and verify that your concurrency limit is reflected as 100. If it is, but your campaign is still queued or you receive concurrency limit emails, open a support ticket with Vapi and include your organization ID, campaign ID, and screenshots of your concurrency settings and error messages. This will help the support team quickly investigate and resolve any backend provisioning issues. Tip: You can also check the Subscription schema to confirm your concurrency limits as seen by the system. Sources: - Outbound campaigns overview - Changelog November 11, 2024
stormy-goldOP•4h ago
still appears the same thing @Duckie
Since your dashboard shows the correct concurrency limit but you still receive "concurrency limit reached" errors and your campaign remains queued, the next step is to open a support ticket with Vapi.
Include your organization ID, campaign ID, and screenshots of your concurrency settings and error messages. This will help the support team quickly investigate and resolve any backend provisioning issues.
You can also reference the Subscription schema to confirm your concurrency limits as seen by the system.
See documentation for more details. Sources: - Outbound campaigns overview - Changelog November 11, 2024
Include your organization ID, campaign ID, and screenshots of your concurrency settings and error messages. This will help the support team quickly investigate and resolve any backend provisioning issues.
You can also reference the Subscription schema to confirm your concurrency limits as seen by the system.
See documentation for more details. Sources: - Outbound campaigns overview - Changelog November 11, 2024