Delivery
Purge content
Purging removes cached content immediately rather than waiting for its TTL to expire — the usual move right after a deploy or content change.
How it works
- Purge from the dashboard by domain, or target a specific cache key
- Purge activity is reflected in cache stats so you can confirm it took effect
- Underlying payloads live under a tenant-scoped key namespace, keeping purges isolated to your workspace
Good to know
- A broad purge (whole domain) is heavier than a targeted key purge — prefer the narrowest purge that solves the problem