What happened
What this says
Current to 12 Oct 26Nightly refresh failed; data stale for 48 hours, blocking account managers from accessing current information. Olivia Grant identified connector sync failure.
Problem: Bas Kuijpers reported on 2026-10-09 that the scheduled overnight refresh did not complete, leaving data two days behind and preventing account managers from accessing current records. Handling: Olivia Grant responded within 53 minutes (within 1-hour SLA for Growth tier) and asked clarifying questions. Internal note identified that the refresh job ran but data freshness query returned stale timestamp, pointing to a mid-sync connector failure. Watch: High urgency due to blocking critical operational workflow. Risk of escalation if not resolved within hours.
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.