What happened
What this says
As at Fri 9 Oct 2026Paul Rigby reported repairs records duplicating during indexing; duplicates persisted after initial fix attempts. Root cause identified as upstream data feed change; permanent fix planned.
Problem: Repairs data was double-counting records during indexing. Paul reported this twice; the first fix did not resolve it, and duplicates persisted after a deployment. Handling: Olivia Grant diagnosed that the upstream repairs data feed structure had changed, causing the indexer to pull duplicates. She rewrote the index parser for a permanent fix rather than a patch. Watch: Data quality issues affecting financial reporting carry high churn risk. Response time was 179 minutes on the initial report.
Details
Updated 9 Oct 26Trail
- created · Paul Rigby 26 Jan 2026 12:40Still double-counting on the repairs jobs. I've reported this twice now and your fixes aren't working. I need this resolved before we report to the board.
- Public reply · Olivia Grant 26 Jan 2026 15:39Hi Paul, I can see you've raised this again. Let me look at why the previous fixes haven't stuck. I'll check the logs and get back to you.
- Public reply · Olivia Grant 28 Jan 2026 10:15I've been digging into this. The issue is the same as before, repairs records are being duplicated during indexing. Let me push a permanent fix this morning and get you the updated data by end of day.
- Public reply · Paul Rigby 30 Jan 2026 10:26Did the fix deploy? I'm still seeing duplicates in this morning's refresh.
- Internal note · Olivia Grant 30 Jan 2026 16:41Fix deployed 28th but live indexer still pulling duplicates. Root cause deeper, upstream repairs data feed changed again. Rewriting the index parser for permanent fix. Deploy by Friday.
- Status change · 6 Feb 2026 23:59