Nightly Refresh Failed – Data Stale
Ticketclosed
Fenmoor Specialty Underwriting · Nightly Refresh Failed – Data Stale
The nightly refresh showed completed in logs but failed to update tables, leaving the data more than one day old. This was blocking capacity provider calls. Bethan Lister and Kieran Walsh identified a database deadlock, cleared the lock, and reran the refresh to restore data on the same day.
What happened
What this says
As at Fri 9 Oct 2026The nightly refresh showed completed in logs but failed to update tables, leaving the data more than one day old. This was blocking capacity provider calls. Bethan Lister and Kieran Walsh identified a database deadlock, cleared the lock, and reran the refresh to restore data on the same day.
Problem: The 07:00 nightly refresh appeared complete in the logs but the tables remained unchanged with stale data (more than one day old). Callum Reid's team flagged this and confirmed their logs showed completion, suggesting the issue was on BG-Demo's platform.
Handling: Bethan confirmed the platform issue and escalated to Kieran. The root cause was a deadlock during table updates. Kieran cleared the lock and reran the refresh, restoring current data.
Watch: This is a service availability and data freshness breach affecting an Enterprise-level SLA commitment. Same-day resolution was effective. Monitor for pattern.
Details
Updated 9 Oct 26Trail
created · Callum Reid 21 Jul 2026 14:20The underwriting dashboard is out of date. The nightly refresh was due at 07:00 but the tables haven't updated. The team flagged this at 07:42 when they came in. It's now afternoon and the data is still not refreshed – it's more than a day old. This blocks our capacity provider calls, which depend on current data. We need the refresh running immediately.- Public reply · Callum Reid 21 Jul 2026 14:39Logs on our end show the refresh completed. But the tables are stale. Something's gone wrong on your platform.
- Internal note · Bethan Lister 21 Jul 2026 14:54Confirmed – refresh logs show completion but table update failed. Likely deadlock or transaction failure. Escalating to Kieran for investigation.
- Public reply · Bethan Lister 21 Jul 2026 15:04Just so I've got this right – the 07:00 refresh didn't update your tables even though the process shows as completed in the logs? I've confirmed the issue on our side. Kieran is investigating the platform logs to find out why the update didn't complete. I'll update you as soon as we've found the cause.
- Public reply · Bethan Lister 21 Jul 2026 15:21Found it. The update process hit a deadlock when writing to the tables. Kieran's cleared the lock and rerun the refresh. Your tables should be current now. Can you check the dashboard and confirm it's showing today's data? Thanks, Bethan
- Status change · 25 Jul 2026 23:59