What happened
What this says
Current to 11 Oct 26Nightly refresh failed after upstream API change, leaving data stale; root cause identified and fix applied for next refresh.
Problem: Nightly refresh did not complete, leaving data stale since the previous morning. Hugh had a presentation the next day requiring current figures.
Handling: Olivia identified upstream API change within 34 minutes and Ewan applied fix in production. Data current after next refresh.
Watch: Enterprise customer with tight timeline expects SLA on data freshness.
Details
Updated 9 Oct 26Priorityhigh
Statusclosed
Categorydata_freshness
Channelemail
First response (min)34
CSAT5
Incidentinc_2026_07_refresh
Helpdeskmade from
Trail
- created · Hugh Fenton 21 Jul 2026 17:07The dashboards haven't refreshed since yesterday morning. We're still seeing data from before the nightly refresh and it's affecting our reporting. Can you look into what happened?
- public_reply · Olivia Grant 21 Jul 2026 17:41Hi Hugh, thanks for reporting this. Just so I've got this right, the nightly refresh didn't complete and your data is stale. I'm looking into this now.
- public_reply · Hugh Fenton 22 Jul 2026 11:19Correct. We have a presentation tomorrow using these figures so this is urgent. What's the timeline to fix?
- internal_note · Olivia Grant 22 Jul 2026 12:42Root cause identified: upstream API changed. Applied fix in production. Data will be current after tonight's refresh.
- status_change · 26 Jul 2026 23:59
Helpdeskmade from