What happened
What this says
Current to 10 Oct 26Craig found duplicate records in the brain that don't exist in source system. Bethan identified root cause in indexing logic, offered and performed one-off cleanup while a fix is prepared for next release.
Problem: duplicate membership records appeared in queries despite clean source data, affecting query accuracy. Handling: Bethan traced the duplicate to the refresh indexing logic and offered a workaround (one-off cleanup) while the product team prepared a fix for the next release. Craig approved the cleanup. Watch: monitor after the fix releases to confirm duplicates don't recur.
Details
Updated 9 Oct 26Trail
- created · Craig Paterson 3 Nov 2025 12:19Hi, I've spotted some duplicated records in the brain that are throwing off the data. When I run a query on membership, I'm getting duplicate entries where there should only be one. I've had a look at the underlying data and the duplicates aren't there, so something's happening on the brain side. Can you take a look? Regards, Craig
- public_reply · Bethan Lister 3 Nov 2025 18:33Hi Craig, I've picked this up. Just so I've got this right – you're seeing duplicate membership records in the brain that don't exist in your source system, yeah? Can you give me an example and I can trace it through the ingestion? Thanks, Bethan
- public_reply · Bethan Lister 5 Nov 2025 13:49Thanks for the example. I've found it. Root cause is a duplicate in how the records are being indexed on refresh. We've got a fix in the pipeline for the next release. In the meantime, we can do a one-off cleanup of your data if you'd like. Do you want me to go ahead with that? Thanks, Bethan
- public_reply · Craig Paterson 5 Nov 2025 15:32That would help, thanks. Go ahead with the cleanup and I'll keep an eye on it after the next refresh. Regards, Craig
- status_change · 23 Nov 2025 23:59