# Asset cache serves old bundle: first 30 minutes checklist

Source: https://releasefailures.com/incidents/asset-cache-serves-old-bundle/
Content version: 1.0.0
Verified on: 2026-10-22
Licence: CC BY 4.0

Definition: Users receive an old JavaScript bundle with a new API and the app errors.
- [ ] FM-01 Query frontend asset requests for 404 responses since the last deploy, because existing alerts may not cover them.
- [ ] FM-02 Ask one affected user whether a hard refresh or a cleared browser cache fixes the page.
- [ ] FM-03 Compare the hashes of the entry file and chunks served at the CDN edge with the hashes in the new build.
- [ ] FM-04 Purge the stale entry file and chunks at the CDN and shorten their cache lifetime.
- [ ] FM-05 Pause further deploys until a change that invalidates cached frontend assets on deploy is in the release branch.
- [ ] FM-06 Decide between a rollback and a hotfix for the un-hashed or uninvalidated files, and record which asset URLs each option changes.
- [ ] FM-07 Tell affected users to hard refresh or clear the browser cache, and post the same steps on the status page.