What happened
What this says
As at Fri 9 Oct 2026Carrowkeel's property records were duplicated with conflicting values, confusing query results. Root cause was a Zendesk connector sync that ran during customer data reconciliation. Resolved by resyncing the connector.
Problem: Siobhán reported duplicate records for several properties with different values, making queries unreliable. Olivia asked for specific examples to trace the source.
Handling: Internal logs revealed the Zendesk connector had synced while the customer was reconciling, picking up both old and new records. Olivia resynced to clean up, resolving the issue by 23 Oct 2025.
Watch: Connector sync during customer data changes can cause duplicates. Pattern monitoring elsewhere would reduce similar reports.
Details
Updated 9 Oct 26Trail
- created · Siobhán Nolan 22 Oct 2025 08:51Hi, We're seeing a data quality issue in the brain. We're getting duplicate records for several of our properties, and I'm seeing multiples of quite a few of them. Some of the duplicates have slightly different values too, which is confusing people when they're running queries. Can you look into what's going on? Thanks, Siobhán
- Public reply · Olivia Grant 22 Oct 2025 10:32Hi Siobhán, Thanks for flagging. Duplicates usually happen when a connector picks up records twice, often because something changed in the source system while we were syncing. Can you give me an example? A property name or ID would help me find the exact duplicates and trace where they're coming from. I'll get onto it now. Olivia
- Internal note · Olivia Grant 22 Oct 2025 14:25Checked logs. Zendesk connector sync ran at 15:15 UTC on 21st. Customer had reconciliation in Zendesk at 15:00 same day, connector picked up both old and new records before dedup logic ran. Resyncing connector now to clean up. Should be resolved by end of business.
- Status change · 27 Oct 2025 23:59