Investigating Issue with Voice Conversation Closure
resolved- Started
- Nov 11, 4:01 PM EST
- Resolved
- Nov 11, 4:38 PM EST
- Duration
- 36 min
Decagon's updates (2)
- update · Nov 11, 4:01 PM EST
We’re currently investigating reports of an issue affecting voice conversation closure. Our team is working to identify the cause and will provide an update shortly.
- resolved · Nov 11, 4:38 PM EST
The issue affecting voice conversation closure has been resolved. This only impacted post-conversation effects, such as automations, so there was no end-user impact for affected conversations. Impact Window: 12:37pm EST, 11/10/26 – 4:38pm EST, 11/11/26 Cause: A code regression introduced failures in voice call cleanup. For a subset of calls in our EU region, the step that marks the conversation as closed failed. Those conversations stayed open in the system after the caller hung up. Our team has backfilled post-call processing on the affected conversations.
What our checks recorded
We checked Decagon 7 times from Decagon's start time to its resolution, once every five minutes. Every one of them reached Decagon's site, so this incident did not show up as a failed page load. Our check loads the public site; it cannot see an API error or a broken feature. Median response time was 124 ms, against 249 ms over the 24 hours before. Decagon posted the incident at Nov 11, 4:01 PM EST.
Updates are Decagon's own words from its status page (status: resolved); we never add an inferred cause.