Data showing several days out of date
Ticketclosed
Brackwell Freight Ltd: documents · Data showing several days out of date
Delivery data was several days stale during Tuesday operations review; nightly refresh appeared to run but data was not current; customer traced issue to delivery connector configuration and self-resolved.
What happened
What this says
Current to 10 Oct 26Delivery data was several days stale during Tuesday operations review; nightly refresh appeared to run but data was not current; customer traced issue to delivery connector configuration and self-resolved.
Problem: Customer depended on nightly refresh by Tuesday morning to spot at-risk contracts. Delivery data lagged several days despite refresh job showing completion. Issue spanned 10 Dec 2024 to early January. Handling: BB-Demo support asked diagnostic questions but did not identify root cause. Customer self-diagnosed the issue to delivery connector configuration and made necessary adjustments, resolving without BB-Demo engineering intervention.
Details
Updated 9 Oct 26Trail
created · Aisha Rahman 10 Dec 2024 16:09Hi, Just flagging an issue with the freshness of the data. This week's Tuesday operations review – which is how we spot at-risk contracts – ran on delivery data from several days ago rather than current figures. I've checked on our end and everything looks fine: the source systems are live, and the connectors are all showing green. I've also run a manual refresh to see if that would pull through the latest data, but we're still getting figures that are out of date by several days. Is it me or should the nightly refresh be bringing in current data by the time of the Tuesday morning report? I've attached a screenshot showing what we're seeing versus what we'd expect. Thanks, Aisha- public_reply · Bethan Lister 10 Dec 2024 23:18Hi Aisha, Just so I've got this right – the data in the brain is running a few days behind the live source system, and that's showing up in your Tuesday operations review. I can see you've already checked the sync logs and run a refresh, which is exactly the right approach. Can you tell me which connector is serving that delivery data? And have there been any recent changes to the source system – a permissions update, a field change, anything like that? Sometimes we see a lag like this when the source system changes and the connector needs to adjust. Thanks, Bethan
- public_reply · Aisha Rahman 12 Dec 2024 09:23Hi Bethan, I've tracked it down to the delivery connector. I've found the issue on our end and made the necessary adjustments. It should come through properly once tonight's refresh completes. I'll keep an eye on the Tuesday report and let you know if anything else looks off. Thanks, Aisha
- status_change · 6 Jan 2025 23:59