Dashboards maintain a 24-hour result cache to optimize initial loading times, operating on a best-effort basis. This means that while the system always attempts to use historical query results linked to dashboard credentials to enhance performance, there are some cases where cached results cannot be created or maintained.
The following table explains how caching varies by dashboard status and credentials:
Dashboard type Caching type
| Published dashboard with embedded credentials | Shared cache. All viewers see the same results. |
| Draft dashboard or published dashboard without embedded credentials | Per user cache. Viewers see results based on their data permissions. |
Dashboards automatically use cached query results if the underlying data remains unchanged after the last query or if the results were retrieved less than 24 hours ago. If stale results exist and parameters are applied to the dashboard, queries will rerun unless the same parameters were used in the past 24 hours. Similarly, applying filters to datasets exceeding 64,000 rows prompts queries to rerun unless the same filters were previously applied in the last 24 hours.
Ajay Kumar Pandey
