Hello! We’re running into a caching issue with FinSweet CMS List Cache (fs-list-cache=“true”) on a production Webflow site.
The CMS items are updated hourly via API and go live without performing a site republish.
However, the cache only clears when the Webflow site is republished, meaning users who are seeing a cached version can encounter outdated CMS data (such as vehicle prices) for days at a time.
One option would be to automatically republish the site whenever the CMS updates via API. This would clear the cache and sync the prices, but it affects all users — not just those with outdated cache — and we’d prefer to retain as much caching as possible for performance reasons.
Therefore, we’re considering writing client-side code to clear the IndexedDB cache if it’s older than a certain age (e.g. 1 hour). We’re unsure if this is safe or supported.
We’d love to know if anyone has tried this approach, or if there’s a better way to keep cached CMS data up to date (e.g. by setting a cache expiry somehow)?
The fs-list-cache="true" attribute stores collection pages in IndexedDB until the site is republished. Currently, Attributes v2 doesn’t include a built-in method to automatically clear this cache on a schedule.
If you want to avoid stale data, you can disable caching entirely by setting fs-list-cache="false" on your list wrapper. This prevents outdated content but removes the performance benefits of caching.
Thanks for your answer, Luis! I think we’ll go with the automated hourly publishing but just wanted to confirm something:
If we add some client-side code to clear the IndexedDB cache if it’s older than 1 hour, is that likely to break Attibutes v2 for the user or is it unsafe in any way?