Broker records showing duplicate entries
Ticketopen
Ardcarne Life Assurance · Broker records showing duplicate entries
Niamh Costello identified duplicate broker records appearing in the brain from a single clean source. Olivia Grant is investigating connector configuration and data ingestion as root cause.
What happened
What this says
As at Fri 9 Oct 2026Niamh Costello identified duplicate broker records appearing in the brain from a single clean source. Olivia Grant is investigating connector configuration and data ingestion as root cause.
Problem: Exact duplicate broker records from a source system with no duplicates at origin. Handling: BG-Demo identified the issue likely stems from the connector's data processing rather than the source, and is reviewing sync configuration and recent logs. Watch: Open investigation into data quality affecting readiness to roll out broker data. Customer needs accuracy confirmation before proceeding.
Details
Updated 9 Oct 26Trail
created · Niamh Costello 5 Oct 2026 13:35Good morning, we've spotted an issue with the broker data coming through. Some broker records are appearing twice in the brain, which is a problem when we're trying to give our distribution teams a single view. It's not widespread but we're seeing it on a couple of hundred records. I've attached a report. Can you look into what's causing this and what we can do about it? Obviously we need accuracy before we roll this out more widely.- Public reply · Olivia Grant 5 Oct 2026 14:52Hi Niamh, thanks for flagging. I've had a look at the report. The duplicates look like they're coming from the source data. Is it possible your broker records system has the duplicates, or could they be merging from two different sources in the same connector? A few questions to help track this down: are all the duplicates exact copies, or are some of them slightly different? And which connectors are feeding the broker data?
- Public reply · Niamh Costello 7 Oct 2026 16:36The duplicates are exact, same broker ID, same details. The broker data comes from a single system, so it shouldn't be duplicating at source. We've checked there and it's clean. So it looks like the brain is doing it. What does good look like for finding where the duplication happens? I need to understand this before we go further.
- Public reply · Olivia Grant 8 Oct 2026 09:59Got it. The issue is likely in how the connector is pulling or processing the data. Let me look into the connector config and the recent sync logs. I'll need to check if records are being ingested twice in a single run or if there's something in how the data is being mapped. Let me dig into that and I'll come back to you tomorrow morning with findings. In the meantime, what's the timeframe you need this sorted by? Is there a go-live date we're working to?