What happened
What this says
As at Fri 9 Oct 2026Rachael Dixon reported two-day-old data even though the refresh appeared to run. Kate Ormerod found a stale connector credential had blocked the CRM sync and fixed it by manual reindex on 22 Jul 2026.
Problem: the refresh ran overnight according to the logs, but the records had not changed, so the customer was relying on data about two days old.
Handling: Kate Ormerod replied within 106 minutes and said some sources had not synced. An internal note by 16:05 that day recorded the root cause and a manual reindex with a triggered refresh.
Watch: The customer-facing reply does not name the cause, and the ticket was solved on 27 Jul 2026. The credential expiry needs a check so the CRM sync does not stall again.
Details
Updated 9 Oct 26Trail
- created · Rachael Dixon 22 Jul 2026 12:07Hi, we're still seeing stale data in the brain. It's now two days old and we're relying on it for decision making. The refresh ran last night according to the logs but the records haven't changed. Can you force a refresh or check what's gone wrong? This is urgent. Cheers, Rachael
- Public reply · Kate Ormerod 22 Jul 2026 13:53Hi Rachael, I can see the refresh completed last night but some of your data sources didn't sync properly. I'm working with our platform team to identify why. I'll update you as soon as we know more. Kate
- Internal note · Kate Ormerod 22 Jul 2026 16:05Root cause: one connector had a stale credential token. Affected the CRM sync. Reindexed manually and triggered refresh. Data current now.
- Status change · 31 Jul 2026 23:59