update -
Hi Vapi Support,
I recently encountered the “Over concurrency limit” error despite having no active or visible sessions in the dashboard. This issue persisted across all assistants, and the only way to restore normal operation was to purchase an additional concurrent line.
While this immediately resolved the issue, it appears the purchase was only necessary because of a stuck or miscounted concurrency counter on your end.
Could you please:
Manually verify and clear any lingering sessions still counted against our organisation.
Confirm our actual active concurrency usage and limits.
Refund or credit the cost of the extra concurrency line since it was required solely to bypass a platform-side fault.
Our account details are:
Organisation ID: 58ca3d2e-e725-47d3-bca6-f2957140fdc7
I appreciate your help in resolving this and would be grateful for confirmation once the credit or refund is processed.