Delays in Conversation Search, Filtering, and Reporting
resolved- Started
- Sep 9, 5:58 PM EDT
- Resolved
- Sep 9, 8:35 PM EDT
- Duration
- 2h 37m
Decagon's updates (4)
- update · Sep 9, 5:58 PM EDT
We have identified an issue causing delayed results when searching or filtering conversations in the dashboard. Analytics, reporting, and filtered data exports may also reflect stale data. The cause is a delay in the data replication pipeline that feeds these surfaces. Live conversations are not affected. The AI agent continues to respond to end users normally, and no conversation data has been lost. Delayed records will appear once replication catches up. We are actively rolling out a mitigation solution. We will provide another update when that's live or in 30 minutes.
- update · Sep 9, 6:46 PM EDT
We are still working to mitigate this issue. Conversation search, filtering, and reporting remain delayed. Live conversations and AI responses are not affected, and no data has been lost.
- update · Sep 9, 7:53 PM EDT
The fix is in progress and currently being deployed. We will confirm here as soon as it is live.
- resolved · Sep 9, 8:35 PM EDT
This issue is resolved. Conversation search, filtering, listing, and alerting in the dashboard are now reflecting realtime data. Live conversations were unaffected throughout, and no conversation data was lost. Records that appeared missing or delayed during the incident are now present. We have deployed a change that serves these dashboard surfaces from a realtime data path, removing them from the delayed pipeline that caused this issue.
What our checks recorded
We checked Decagon 31 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 170 ms, against 195 ms over the 24 hours before. Decagon posted the incident at Sep 9, 5:58 PM EDT.
Updates are Decagon's own words from its status page (status: resolved); we never add an inferred cause.