Skip to content

Pushed update, old version still cached at the edge

Edge cache often outlives your page cache. Purge makes the change visible immediately.

Try this first

  1. 1Purge selectively per URL or extension when possible
  2. 2For major releases, purge-all with timing in mind
  3. 3Bake cache-busting into the build (hashed filenames)
  4. 4Tune cache headers per asset (static long, HTML short)

When to bring us in

On Vercel, deploy auto-triggers a purge, no manual step needed.

See also

None of the above fits?

Describe your situation below. We pass your input plus the steps you already saw to our AI and return tailored next-step advice. If it's too risky to DIY, we'll say so.

Who are you?

For the AI question we need your email and company, so we can follow up if the AI gets stuck, and to prevent abuse.

Limited to 2 questions per hour and 5 per day, kept lean so the AI stays useful. For more, contacting us directly works better for you and us.

Or skip the DIY entirely

Our Managed IT clients do not look these things up. One point of contact, a fixed monthly price, resolved within working hours.