What happened
What this says
Current to 10 Oct 26Sanne Bakker reported the fifth late refresh in six weeks and demanded a concrete timeline for resolution. Bethan asked Arjun Nair to run a full diagnostic on the refresh pipeline and commit to a fix date.
Problem: five late refreshes in six weeks, with Sanne now escalating the demand from troubleshooting to contract resolution. Handling: Bethan committed to a full diagnostic from Arjun and a fix date by end of week (6 Jul 2026). Acknowledged this cannot continue and escalated from workaround to root-cause. Watch: Sanne's language has shifted from 'can you fix' to 'we need a timeline'; this signals imminent renewal risk. Multiple breaches of the 07:00 SLA have eroded confidence and moved the issue from operational to contractual.
Details
Updated 9 Oct 26Trail
- internal_note · Bethan Lister 6 Jul 2026 10:14Fifth late refresh in six weeks. Sanne asking for fix timeline now. Contract risk. Need Arjun to pull full diagnostic on refresh pipeline and root cause.
- created · Sanne Bakker 6 Jul 2026 12:47Refresh running late again. This is becoming unworkable. We need a concrete timeline on when this will be fixed.
- public_reply · Bethan Lister 6 Jul 2026 14:03I've pulled the logs and asked Arjun to run a full diagnostic on the refresh pipeline and your account's ingestion rate. I understand this has been happening too often and I want to give you a proper answer, not another workaround. I'll have the full picture and a fix date by end of this week. Thanks, Bethan
- status_change · 14 Jul 2026 23:59