Concurrency values were not resetting as expected.
none- Started
- Aug 25, 3:15 PM EDT
- Resolved
- Aug 25, 3:15 PM EDT
- Duration
- —
Retell AI's updates (1)
- resolved · Aug 25, 3:15 PM EDT
Starting from 10:25am to 11:23am, for some customers concurrency was not resetting correctly, causing some calls to fail to connect. We are mitigating the issue by manually resetting concurrency, so the dashboard may not reflect the actual current value. We identified the root cause to be a case where audio file manipulation led to a full disk usage under a corner case scenario, and a fix is deployed.
Updates are Retell AI's own words from its status page (status: resolved); we never add an inferred cause. The vendor's incident page ↗