Retell AI: Concurrency values were not resetting as expected.
Timeline of updates
- resolved
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.
Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab).