Duplicate records in search results
Ticketclosed
Ardenmore Pension Administration · Duplicate records in search results
Harjit Bains reported duplicate customer records appearing in search results on 27 Oct 2023, affecting trustee report accuracy. Callie Brennan reproduced the issue and escalated to engineering; ticket closed 4 Nov 2023 without resolution confirmation.
What happened
What this says
Current to 14 Oct 26Harjit Bains reported duplicate customer records appearing in search results on 27 Oct 2023, affecting trustee report accuracy. Callie Brennan reproduced the issue and escalated to engineering; ticket closed 4 Nov 2023 without resolution confirmation.
Problem: Harjit discovered duplicate records appearing in search results, especially problematic for trustee-meeting reports.
Handling: Callie Brennan reproduced the issue on 27 Oct 2023 and identified a connector loading records twice. She escalated to engineering and promised a fix within a couple of days. Harjit asked on 30 Oct 2023 whether a workaround existed and expressed concern about the trustee meeting. The ticket closed on 4 Nov 2023 without documented confirmation of the fix.
Watch: Data quality issue blocking governance reporting; no follow-up confirms whether the fix was deployed or the duplicate issue recurred. Harjit's last message shows concern but no recorded response thereafter.
Details
Updated 9 Oct 26Trail
created · Harjit Bains 27 Oct 2023 08:19Hi, I'm noticing something odd when I search in the brain. The same customer records are appearing twice in the results - sometimes more. It's not critical, but it's making reports a bit messy, especially when we're pulling data for trustee meetings. Did this start after a system change on our end, or is it something you've seen before?- public_reply · Callie Brennan 27 Oct 2023 13:50Hi Harjit, thanks for flagging that. I'll investigate. Can you give me an example search query that's showing the duplicates? That'll help me work out exactly what's happening.
- public_reply · Callie Brennan 27 Oct 2023 14:36I've reproduced the issue. Looks like there's a connector loading records twice. I'm escalating to the engineering team and we should have a fix within a couple of days. Will update you as soon as we hear more.
- public_reply · Harjit Bains 27 Oct 2023 16:49Thanks Callie, appreciate the quick investigation. Is there a workaround we can use while you're working on the fix, or should we just be careful with what we pull into reports?
- public_reply · Harjit Bains 30 Oct 2023 13:15Just checking in - any update on the duplicate records? We have a trustee meeting coming up and I want to make sure the data's clean before we use it in the analysis.
- status_change · 4 Nov 2023 23:59