Report Dashboard Caching
Friday, August 7, 2026
What it is
Lets users control how long reporting dashboards hold cached data, from five minutes to seven days, so dashboards load faster, with manual refresh still available. It is off by default; turn it on from a dashboard's actions menu under cache settings. A last-updated timestamp appears in the lower right of each report.
Why it matters
Complex dashboards can be slow to reload even when the underlying data has not changed. Caching reduces unnecessary reloads while letting you choose a refresh cadence that fits how the dashboard is actually used.
The Take
Chris Carolan
Caching reads like a performance feature, and the thing it actually fixes is the refresh you did not ask for.
Caching reads like a performance feature and it is not. The thing it actually fixes is the refresh you did not ask for, arriving while you are mid-meeting or while someone is presenting from a PDF that was accurate when it generated and no longer matches what is on the screen. Somebody asked for a real-time dashboard, got one, and the gap between two versions of the same number is what creates the friction.
Coming off a build where the dashboards are complex, including a unified revenue view, the seven-day ceiling matters more than the five-minute floor. Most reports can wait a day and nobody notices. Where latency actually bites is during testing, when you have changed something and need to know whether it took, and that is exactly the window a long cache works against. Set it per dashboard, not per portal.
Watch Us Discuss This
The full segment from the show, us working through this update start to finish.
Produced by Value-First Media