Duplicate property records
Ticketclosed
Carrowkeel Software: documents · Duplicate property records
Property records duplicated because sync layer treated updates as new records. Bethan identified root cause; manual refresh cleared duplicates.
What happened
What this says
Current to 12 Oct 26Property records duplicated because sync layer treated updates as new records. Bethan identified root cause; manual refresh cleared duplicates.
Problem: Property records appeared twice with the same reference, causing inaccurate reports for the customer success team. Root cause: The sync layer created new records instead of updating existing ones. Handling: Bethan reproduced the issue, escalated to Felix on the platform team, and advised a manual refresh. Customer ran the refresh on 4 Dec 2025 and confirmed resolution. Watch: Updates to connectors or sync logic need regression testing on high-volume tables.
Details
Updated 9 Oct 26Trail
created · Siobhán Nolan 2 Dec 2025 15:29Hi, we're seeing duplicate property records in the brain when we query our portfolio data. Several properties are showing up twice with the same reference code. This is affecting our customer success team's ability to pull accurate reports. Can you help investigate?- public_reply · Bethan Lister 2 Dec 2025 20:16Thanks, Siobhán. I can help. Just so I've got this right, property records are duplicating in the brain, showing up twice with the same reference. Can you send me a few examples so I can check our logs and the Snowflake instance? Thanks, Bethan
- public_reply · Siobhán Nolan 3 Dec 2025 16:04Sure. We're seeing it in properties synced over the last few days, especially ones our team updated. Looking at it more, it seems like it might be in the sync layer. Let me send you the list of affected properties tomorrow morning.
- public_reply · Bethan Lister 4 Dec 2025 10:08Thanks, Siobhán. I've checked the logs and reproduced the issue. Each property update is creating a new record instead of updating. The root cause is in the sync layer. I'm escalating this to our platform team now. Can you try running a manual refresh of that connector in the meantime? Thanks, Bethan
- internal_note · Bethan Lister 4 Dec 2025 15:23Root cause: sync layer treating updates as new records rather than updates. Escalated to Felix. Customer running manual refresh. Monitoring for recurrence.
- public_reply · Siobhán Nolan 4 Dec 2025 15:30Perfect! We ran the manual refresh and the duplicates have cleared. Data's looking good now. Thanks for getting on this so quickly.
- status_change · 8 Dec 2025 23:59