What happened
What this says
As at Fri 9 Oct 2026Aaron Crowther reported pipeline numbers stale on 19 Sep 2024 after a late refresh. The default view had cached a stale snapshot; BG-Demo cleared the cache and flagged it to the team.
Problem: Aaron Crowther said placements from the day before were missing from the default view, and the refresh seemed to stop before 07:00. Filtering to the last ninety days showed them.
Handling: Bethan Lister's internal note says the default view cached a stale refresh snapshot after a late run, which Arjun Nair confirmed from the job log as a queue delay. The cache was cleared on the customer's tenant on 20 Sep 2024.
Watch: Every tier carries a 07:00 nightly refresh commitment, so a late run is a service issue. The record does not show whether Aaron was told the cause or whether the cache issue reached the product team.
Details
Updated 9 Oct 26Trail
- created · Aaron Crowther 19 Sep 2024 12:25Our candidate pipeline numbers look stale this morning. The last refresh seems to have stopped before 07:00 and some placements from yesterday are missing. We have a busy week so this needs fixing quickly. Thanks, Aaron
- Public reply · Bethan Lister 19 Sep 2024 14:55Hi Aaron, sorry for the trouble. I can see the refresh finished late for your account today. Can you check whether the missing placements show when you filter by date? If they do, that's a display issue on our side and I'll look into it. Thanks, Bethan
- Public reply · Aaron Crowther 20 Sep 2024 10:25Hi Bethan, yes, they show when I filter to the last ninety days but not on the default view. Did you find anything?
- Internal note · Bethan Lister 20 Sep 2024 16:43Default view cached a stale refresh snapshot after the late run. Cache cleared on their tenant. Arjun checked the job log and the late run was a queue delay. Worth flagging the default view cache to the team.
- Status change · 24 Sep 2024 23:59