# Retell AI: Concurrency values were not resetting as expected.

- Impact (vendor’s label): none
- Status: resolved
- Started: 2025-08-25 19:15 UTC · Resolved: 2025-08-25 19:15 UTC · Duration: 0 min
- Updates: 1
- [Vendor status page: https://stspg.io/0fprz2kvlg83](https://stspg.io/0fprz2kvlg83)
- [Company: Retell AI](https://rewindex.com/company/retell-ai.md)

## Timeline of updates

- **resolved** 2025-08-25 19:15 UTC: 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.


---
Canonical: https://rewindex.com/company/retell-ai/incidents/96py9pfytj5h · Markdown: https://rewindex.com/company/retell-ai/incidents/96py9pfytj5h.md · JSON: https://rewindex.com/api/v1/companies/retell-ai/incidents/96py9pfytj5h · Generated 2026-10-20T00:06:06.863Z