Repairs data mismatches between brain and source system
Ticketclosed
Calderbrook Housing Group · Repairs data mismatches between brain and source system
Paul reports repairs records showing wrong statuses and missing jobs since the housing system upgrade. Olivia identifies records stuck during nightly refresh.
What happened
What this says
As at Fri 9 Oct 2026Paul reports repairs records showing wrong statuses and missing jobs since the housing system upgrade. Olivia identifies records stuck during nightly refresh.
Problem: Paul reported repairs data mismatches starting after the housing system upgrade - records showing closed in brain but in progress in source, some job numbers missing entirely. Data was unreliable for reporting.
Handling: Olivia investigated, identifying that nightly refresh was not syncing records fully post-upgrade. Some records were stuck in the pipeline, others out of sync with source statuses. The internal note recommended investigating refresh logic, resetting the connector, or checking field mappings.
Watch: This ticket opened a series of repairs connector issues (tickets 0012-0016). The pattern suggests the housing system upgrade exposed a vulnerability in how the connector handles schema changes.
Details
Updated 9 Oct 26Trail
created · Paul Rigby 24 Feb 2026 13:13Our repairs report from the brain is showing mismatches with the housing system. Not just duplicates now, some jobs are missing, others showing different statuses. The data's unreliable. We need it to match exactly for our reports. Paul- Public reply · Olivia Grant 24 Feb 2026 16:19Hi Paul, I can see there are discrepancies on repairs records now. To help me understand the scope of the issue, can you share a few examples of jobs with mismatches? Specifically, which ones are missing and which ones have wrong statuses?
- Public reply · Paul Rigby 26 Feb 2026 15:56Records showing as closed in the brain but in progress in the source. Some job numbers aren't coming through at all. It's not consistent. Hard to trust the data when it doesn't match the source.
- Public reply · Olivia Grant 27 Feb 2026 09:21Thanks for that. I've been looking into the mismatch patterns. It seems some records are getting stuck during the nightly refresh since the housing system upgrade. Can you confirm when you last saw these mismatches, are they still occurring today?
- Public reply · Paul Rigby 27 Feb 2026 12:34Yes, they're still happening today. I checked this morning and the mismatches are still there. This needs sorting soon.
- Internal note · Olivia Grant 27 Feb 2026 13:00Mismatches ongoing since housing system upgrade. Records not syncing fully in nightly refresh. Some jobs stuck in pipeline, others with status out of sync. Needs investigation of refresh logic post-upgrade. May need to reset connector or check field mappings.
- Status change · 8 Mar 2026 23:59