Caching behaviour

[mdenison]

I am not quite sure if I am reading the documentation wrong or not understanding the caching mechanism with Apache Superset completely.

We have multiple dashboards, datasets, charts etc. running Superset 6.0.0.

The DATA_CACHE_CONFIG and FILTER_STATE_CACHE_CONFIG both use S3Cache. If I assume correct, the default setting for the CACHE_DEFAULT_TIMEOUT is 86400?

But, on some Charts, when opening the breadcrumb, it states "Cached 5 days ago". But, when I look at the payload which comes from api/v1/chart/data. I get following payload:

    "result": [
        {
            "cache_key": "7a2843791d728e0163b00b345ee35bb0",
            "cached_dttm": "2026-02-26T09:58:22",
            "cache_timeout": 86400,
            "applied_template_filters": [],
            "annotation_data": {},
            "error": null,
            "is_cached": true,`
............

I would assume that the cached_dttm is compared with the cache_timeout in combination with todays date when generating a cache_key from the SQL Query.

The Data is refreshed without issues when clicking "Force refresh", but I guess that is not intended when the cache should be invalidated?

[mdenison]

In case anyone ever stumbles across a similar issue. Dosu pointed me in the right direction in this Issue: #38605 . So, nothing what was wrong with Apache Superset. But an unmaintained Python lib which was used to cache data in S3.