What happened
What this says
As at Fri 9 Oct 2026Client records hadn't updated for 24 hours. Bethan Lister identified the connector sync failed at 06:47 on 9 Feb 2026, restarted it, and queued a full refresh.
Dan reported client records were 24 to 48 hours out of date despite the nightly refresh running. Orders and other data were current, isolating the issue to the client connector.
Bethan investigated and found the connector sync had failed during its cycle on 9 Feb 2026. She restarted it and queued a full refresh but no customer confirmation of resolution is shown.
The ticket shows data freshness as medium urgency. First response was 357 minutes from creation.
Details
Updated 9 Oct 26Trail
- created · Dan Hosken 9 Feb 2026 14:17The client data in the brain hasn't refreshed since yesterday morning. We're looking at records that are a day or two out of date, which isn't helpful when we need current information for our daily work. Is there an issue with the refresh process?
- Public reply · Bethan Lister 9 Feb 2026 20:14Thanks for reporting this. Just so I've got this right, the client records aren't showing updates from the last 24 hours? Let me check the refresh logs on our side. Can you tell me: is this affecting all your connectors or just the client records? Thanks, Bethan
- Public reply · Dan Hosken 11 Feb 2026 09:44It's the client data mainly. Everything else looks current. I've checked through yesterday and today and the dates haven't moved.
- Internal note · Bethan Lister 11 Feb 2026 11:04Checked ingestion logs. Client connector sync failed 9 Feb 2026 06:47. Restarted connector. Full refresh queued.
- Status change · 21 Feb 2026 23:59