Introduction

When Cloudflare cache does not clear after an update, the site can look half-deployed. Some users see fresh content while others still get old HTML, CSS, JavaScript, or API responses from edge cache. The real fix is to understand which layer is still serving stale data and why that object remains eligible for reuse.

Symptoms

  • Design or content changes appear at origin but not on the public site
  • Purging cache seems to work briefly or not at all
  • CSS and JavaScript updates fail to appear for some users or regions
  • HTML pages update inconsistently while assets remain stale
  • The issue started after adding cache rules, APO, or aggressive edge caching

Common Causes

  • Cloudflare cache rules still allow the stale object to be reused after deployment
  • Origin cache headers mark HTML or assets as cacheable longer than intended
  • Purges target only part of the affected URL set
  • Asset filenames do not change, so browsers and edge caches reuse old versions
  • Another layer such as application cache or upstream CDN still serves previous content

Step-by-Step Fix

  1. Identify whether the stale response is HTML, an asset, or an API payload, because each may be cached differently.
  2. Compare response headers from the browser, Cloudflare, and origin to see where the stale object is being reused.
  3. Review Cloudflare cache rules, APO settings, and page-level behavior that might override normal origin cache control.
  4. Confirm the purge scope matches the affected content, especially if the deployment changed multiple URLs or shared assets.
  5. Check whether asset versioning is in place so browsers and edges request a new filename after each release.
  6. Test the origin directly to confirm the updated content is actually available before blaming the edge cache.
  7. Purge the precise stale URLs or perform a broader purge only after you know which cache layer remains out of date.
  8. Retest from a clean browser session and, if possible, from more than one region to confirm old edge objects are gone.
  9. Adjust cache strategy so HTML, assets, and API responses each get explicit freshness rules instead of one broad default.