What happened
What this says
As at Fri 9 Oct 2026Paul Rigby reported repairs jobs double-counted again since the housing system upgrade. Each job appears twice across the board, hitting dashboards before morning stand-up. Arjun Nair traced it to post-upgrade mapping creating one-to-many joins; fix in hand.
Problem: Paul raised the same duplicate repairs issue again. The post-upgrade connector mapping is creating one-to-many joins on job IDs, causing duplication across all dashboards before the morning stand-up.
Handling: Arjun traced the root cause to the post-upgrade mapping logic, not the data feed itself. Fix ready to deploy. Olivia explained the cause and committed to rolling it out.
Watch: This is the second ticket for the same issue in nine days. Paul is frustrated by recurrence. The root cause has evolved from ingest format to join logic, suggesting the first fix did not fully address the underlying integration change.
Details
Updated 9 Oct 26Trail
- Public reply · Paul Rigby 19 Jan 2026 10:24Double-counted again in this morning's report, jobs appearing twice. Spreadsheet attached. Can you look into this?
- created · Paul Rigby 19 Jan 2026 12:54Double-counted again. Since the housing system upgrade, repairs jobs are appearing twice across the board. Spreadsheet attached with the full list. Hitting the dashboards before the morning stand-up. This needs fixing.
- Public reply · Olivia Grant 19 Jan 2026 15:25Thanks for flagging this, Paul. Just to clarify, when did you first notice this happening? Was it straight after the upgrade went in?
- Internal note · Olivia Grant 21 Jan 2026 15:29Arjun traced it. Post-upgrade mapping creating one-to-many joins on job IDs. Fix ready.
- Public reply · Olivia Grant 21 Jan 2026 15:58Paul, root cause is the post-upgrade mapping, creating one-to-many joins in the job ID reconciliation. Arjun's got a fix in hand. Once that's live, give it a try and let me know how it goes.
- Status change · 27 Jan 2026 23:59