Hey GD Team, I am noticing an issue where dashboard visualisation data was showing some outdated data (it was a snapshot of a week ago). I edited a visualisation in the dashboard by adding a new field, and the data was immediately refreshed after I made this change and saved it. The expectation is obviously for the visualisation data to be up to date to the latest refresh (we run the pipeline once an hour) - is there a bug on your end? Can you please advise?

Thank you for your detailed description. Based on the information in the knowledge sources, what you are experiencing is most likely related to GoodData’s caching mechanism rather than a bug. By default, GoodData Cloud does not automatically refresh data from the data source on a set schedule. Instead, it uses a cache that is invalidated only when you explicitly trigger a cache reload (for example, via API, Python SDK, or manually in the data source UI). There is no built-in time-to-live (TTL) for the cache; it is evicted based on a least recently used (LRU) policy. This means that unless you or your automation pipeline explicitly invalidates the cache after your data pipeline runs, dashboards and visualizations may show stale data—even if your underlying data source is up to date. Editing a visualization or making changes to the dashboard can sometimes trigger a cache refresh, which is why you saw the data update immediately after your edit. This is expected behavior, not a bug, but it can be confusing if you expect data to always be current with your pipeline schedule. If you require up-to-date data after each pipeline run, you should automate cache invalidation using the provided API or SDK. Alternatively, you can set your data source to "DirectQuery" mode (if supported), which bypasses the cache and always queries the latest data from your database, but this may have performance implications. There is currently no way to set a cache expiration timeout that would automatically refresh the cache after a certain period—manual or automated invalidation is required for up-to-date data display. For more details, see the documentation and related discussions: [Cache Management in GoodData Cloud](https://www.gooddata.com/docs/cloud/connect-data/cache-management/) [Reload Cached Data](https://www.gooddata.com/docs/cloud/connect-data/cache-management/reload-cached-data/) [Community discussion on cache and data freshness](https://gooddataconnect.slack.com/archives/C04S1MSLEAW/p1741349787092699?thread_ts=1741349787.092699&cid=C04S1MSLEAW) If you have already automated cache invalidation and still see stale data, consider checking for browser-level caching issues, especially if your dashboards are embedded in an iframe. In such cases, users may need to perform a hard reload or clear cookies to see the latest data, as browser caches can sometimes serve outdated content even after backend cache invalidation. More on this can be found in this discussion: [Frontend cache staleness and invalidation](https://gooddataconnect.slack.com/archives/C04S1MSLEAW/p1750092828192749?thread_ts=1750092828.192749&cid=C04S1MSLEAW) In summary: - GoodData does not auto-refresh dashboard data unless you automate cache invalidation. - Editing a visualization can trigger a cache refresh, which explains the behavior you observed. - For real-time or near real-time data, use DirectQuery or ensure cache invalidation is part of your pipeline. - If you continue to see stale data, check for browser caching issues. If you need further assistance or suspect a different issue, please provide more details about your data source configuration and cache invalidation process.

What's the best practice here?

Hi Raffaella, as our Ai assistant mentioned, there is no auto-refreshed data unless you automate cache invalidation. So the best practice here is to automate the Cached Data. GoodData stores computed results for your analytics in an internal cache. However, if new data arrives to the database, you need to refresh this cache to ensure your visualizations display the latest data. And as mentioned in the below documentation: We recommend automating the notification process so that every time your database is updated, the API or Python function is executed automatically. https://www.gooddata.com/docs/cloud/connect-data/cache-management/reload-cached-data/

Thanks for confirming Michael