What happened
What this says
As at Fri 9 Oct 2026Rachael reported data was still two days old even after nightly refresh completed. Kate identified a stale credential token in one connector and manually reindexed the data.
Problem: Rachael Dixon reported that despite the nightly refresh completing, her data remained two days old and unchanged, still blocking decision-making.
Handling: Kate found that one connector had a stale credential token that blocked the CRM sync. She manually reindexed the affected data and triggered a refresh, restoring current data.
Watch: This is the continuation of incident inc_2026_07_refresh, showing the first resolution was incomplete. Credential rot is a recurring risk for connectors requiring token refresh. Monitor whether stale credentials have recurred and whether Tarnbeck has strengthened credential management.
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