What happened
What this says
Current to 11 Oct 26Claims records appearing as duplicates after Salesforce sync frequency increased; deduplication rule configured to fix.
Problem: Claims appearing twice with different dates, affecting monthly claims analysis. Handling: Customer identified Salesforce sync frequency increase as likely cause. Bethan confirmed: more frequent updates created duplicates instead of replacements. Configured deduplication rule for next refresh. Watch: Customer operational change triggered data issue.
Details
Updated 9 Oct 26Prioritynormal
Statusclosed
Categorydata_quality
Channelemail
First response (min)409
CSAT3
Helpdeskmade from
Trail
- created · Aoife Tuohy 25 Aug 2026 11:20Hi, I'm seeing duplicate records in our claims data. It looks like some claims are appearing twice with slightly different dates, which is messing up our reporting. This is a serious issue for us because we're using the brain for our monthly claims analysis. Can you help us figure out where these duplicates are coming from?
- public_reply · Aoife Tuohy 25 Aug 2026 14:20I think I found the issue: it looks like the claims import is pulling in both the original record and an updated version, so we're getting doubles. Can you check if this is a known issue with the Salesforce connector when records are modified?
- public_reply · Bethan Lister 25 Aug 2026 18:09I've picked this up, Aoife. Can you try something for me? Can you tell me exactly which claims are duplicated and what the date difference is between them? Also, have you recently made any changes to how the Salesforce records are being updated? Once I see the specific records, I can check whether this is a deduplication setting we can adjust. Thanks, Bethan
- public_reply · Aoife Tuohy 27 Aug 2026 10:57I've checked a few examples: one claims record appears to be duplicated, with versions a day or two apart but the same amount. And yes, we did change the update frequency in Salesforce to sync more often. Could that be causing the issue?
- public_reply · Bethan Lister 27 Aug 2026 12:01That's really helpful, thanks. The more frequent sync is likely the culprit. When Salesforce records get updated, the connector is treating each version as a new record instead of an update. I can see how to fix this, it's a deduplication rule we can configure. Let me set that up on our end and it should clear the duplicates out of the next refresh. Thanks, Bethan
- status_change · 31 Aug 2026 23:59
Helpdeskmade from