What happened
What this says
As at Fri 9 Oct 2026Customer reported dashboard summary cards intermittently showing inconsistent totals; support ruled out cache and timezone issues; escalated to platform team.
Problem: Bas reported dashboard summary cards showing different record totals than underlying data, occurring intermittently. Handling: Bethan ruled out browser cache and timezone issues, then escalated to Felix Dorran with notes about suspected caching issue in the aggregation pipeline. First response was 277 minutes. Watch: The ticket closed but evidence does not confirm actual resolution. Unresolved data accuracy issues undermine customer confidence.
Details
Updated 9 Oct 26Trail
- Public reply · Bas Vermeulen 24 Sep 2025 09:27I notice this happens intermittently. Sometimes the total is correct, sometimes it's off by a few records.
- created · Bas Vermeulen 24 Sep 2025 13:06One of our dashboards is showing inconsistent totals in the summary card. When I manually count the records, I get a different number than what the dashboard displays. Is this a data freshness issue or something else?
- Public reply · Bethan Lister 24 Sep 2025 15:22Thanks for the detail. Just so I've got this right - you're seeing the summary card total not matching the underlying data sometimes. Can you try clearing the cache by refreshing your browser and tell me if the count updates? Thanks, Bethan.
- Public reply · Bethan Lister 24 Sep 2025 17:43I've also checked if it might be a timezone issue with how we're filtering the date range. Can you share the exact filter settings you're using in that dashboard? Thanks, Bethan.
- Public reply · Bas Vermeulen 25 Sep 2025 12:19Cleared the cache and the issue persists. The filter is date-based, looking at a rolling monthly window. I'll double-check the query logic, but this seems like a calculation issue on your side.
- Internal note · Bethan Lister 25 Sep 2025 14:37Felix to review dashboard aggregation query. Inconsistent record count in the summary widget when using rolling monthly filter. Not timezone-related. Likely a caching issue in the aggregation pipeline.
- Status change · 20 Oct 2025 23:59