What happened
What this says
As at Fri 9 Oct 2026The nightly refresh did not finish, leaving Brinkerhof Distributie data two days old and blocking account managers. It was escalated to Ewan Pryce and is still pending in the record.
Problem: Bas Kuijpers reported that the overnight refresh did not complete, so the data was two days behind and blocking account managers.
Handling: Olivia Grant replied 53 minutes after the ticket opened and asked for error details. She found the refresh job had completed but the freshness query returned a stale timestamp, suspected a connector that stopped mid-sync, and escalated to Ewan Pryce.
Watch: The evidence does not show Brinkerhof Distributie's tier, so the first response time is not judged. The customer's 13:39 comment is timed before the 14:02 creation time, so the record times do not agree.
Details
Updated 9 Oct 26Trail
- Public reply · Bas Kuijpers 9 Oct 2026 13:39The overnight refresh didn't complete this morning. Data is now two days behind. This is blocking the account managers from doing their work. Need this sorted urgently. Bas
- created · Bas Kuijpers 9 Oct 2026 14:02Hi, I'm checking the data and it's stale, records are from two days ago. The nightly refresh should have completed yesterday morning but it looks like it didn't finish. Our account managers need today's data to do their jobs properly. Can you check what's happening with the refresh? Bas
- Public reply · Olivia Grant 9 Oct 2026 14:55Hi Bas, got it. Can you tell me if you're seeing an error message in the refresh logs, or is it just that the data timestamp hasn't moved? That helps me know where to look. I'll check our end too. Olivia
- Internal note · Olivia Grant 9 Oct 2026 15:40Checked platform logs, refresh job completed but data freshness query returning stale timestamp. Connector may have stopped mid-sync. Escalating to Ewan.