What happened
What this says
Current to 11 Oct 26Duplicate records reappeared after the previous fix. Housing system made a second export change, causing deduplication key mismatch; connector logic was updated to handle the new field structure.
Problem: Duplicates returned four days after the first fix was deployed. Handling: Olivia Grant checked connector logs and found deduplication was running but the housing system made another export format change with a new field added. Deduplication key no longer matched the new structure. Connector logic was updated to handle the new field structure. Watch: Second failure in one week suggests housing system changes are frequent or inadequately documented.
Details
Updated 9 Oct 26Trail
- public_reply · Paul Rigby 19 Jan 2026 10:24Hi, the duplicates are back. Repairs jobs appearing twice again. Is the fix you put in still live, or has it been rolled back?
- created · Paul Rigby 19 Jan 2026 12:54Double-counted again. Thought we fixed this? Jobs from the housing system coming through twice. Started again yesterday. This needs to stay fixed this time.
- public_reply · Olivia Grant 19 Jan 2026 15:25Thanks for letting us know. I've checked the connector logs and the deduplication is still running. Can you give me a job reference that's currently duplicated so I can trace it through?
- internal_note · Olivia Grant 21 Jan 2026 15:29Connector dedup is live but housing system made another export change. New field added, causing dedup key mismatch. Arjun updating dedup logic to match on new field structure.
- public_reply · Olivia Grant 21 Jan 2026 15:58Root cause found. The housing system made another change to the export format last week and our deduplication key was matching on the old field. We're updating the logic to handle the new structure. Fix should be live by end of tomorrow.
- status_change · 27 Jan 2026 23:59