Voice agent calls timing out at silence timeout

Timeline

1. ResolvedJul 10, 2026 at 2:48AM

   This incident is resolved. Working with LiveKit, correct call termination at the silence timeout has been restored — calls are once again ending as expected, and recordings are processing and parsing normally. If you had runs that timed out during the incident window, please reach out to support and we can help re-examine them. Thank you for your patience.

2. IdentifiedJul 9, 2026 at 10:16PM

   We're still actively working on the fix alongside LiveKit. We expect calls to be terminating correctly again over the coming hours and will update this page the moment the fix is deployed. Thank you for your patience.

3. IdentifiedJul 9, 2026 at 4:45PM

   We're continuing to work with LiveKit on a fix. Some new calls may still be affected in the meantime; if a run times out, affected runs can be re-examined once service is fully restored. We'll post another update as soon as the fix is live.

4. IdentifiedJul 9, 2026 at 12:30PM

   We've traced this to changes LiveKit introduced over the past ~24 hours that affect Roark's ability to end a call once the silence timeout is reached — which produces both the timeouts and the incomplete recordings described above. We're working directly with LiveKit on a resolution and expect to be back up and running over the next few hours.

5. IdentifiedJul 9, 2026 at 8:40AM

   We've identified the issue. In some cases, LiveKit WebRTC sessions are not being terminated once they reach the silence timeout. This causes the affected call to hang and eventually time out, and can leave an incomplete recording that we're unable to process. We're working on a fix.

6. InvestigatingJul 9, 2026 at 7:05AM

   We're investigating reports of voice agent calls timing out during runs. In affected cases the agent delivers its introduction, but the call then times out, and call details or recordings may be unavailable afterward. We're actively looking into it and will update shortly.