What happened
What this says
Current to 11 Oct 26Data refresh failed due to configuration drift. Bethan deployed a fix, recovered the data and offered a post-incident review to prevent recurrence.
Problem: dashboards stale overnight after a promised fix; Pieter van Dam demanded answers about the failure. Handling: Bethan confirmed the fix had deployed and data was current by 07:00, identified configuration drift as the root cause, and offered a call with the platform team to review prevention measures.
Details
Updated 9 Oct 26Priorityurgent
Statusclosed
Categorydata_freshness
Channelweb
First response (min)25
CSAT2
Incidentinc_2026_07_refresh
Helpdeskmade from
Trail
- public_reply · Bethan Lister 22 Jul 2026 10:54The refresh issue from yesterday is resolved. We deployed a fix and the system ran successfully at 07:00 this morning. Can you check your dashboards and confirm you're seeing current data? Thanks, Bethan
- public_reply · Pieter van Dam 22 Jul 2026 12:36I am seeing data from this morning now. But I need answers about what went wrong. We can't have our reporting going down without warning.
- created · Pieter van Dam 22 Jul 2026 13:03The data is still out of date this morning. Our dashboards haven't refreshed despite what I was told yesterday. This isn't acceptable. How did this happen and what are you doing to make sure it doesn't happen again?
- public_reply · Bethan Lister 22 Jul 2026 13:28Fair point. Configuration drift was the root cause and it shouldn't have slipped through our checks. I've flagged this with our platform team to strengthen the safeguards. Can we schedule a call with you, me, and someone from our platform team to walk through what happened and our prevention plan? Thanks, Bethan
- internal_note · Bethan Lister 22 Jul 2026 15:00Config drift root cause identified. Safeguard improvements raised with platform team. Customer wants post-incident review call. Schedule for next week.
- status_change · 26 Jul 2026 23:59
Helpdeskmade from