You can now invalidate CDN cache contents by tag.
This marks all cached content associated with the tag as stale. The next request serves stale content instantly while revalidation happens in the background, with no latency impact for users.
There are several ways to invalidate content:
In addition to invalidating by tag if the origin content changes, you can also delete by tag if the origin content is gone. However, deleting the cache can increase latency while new content is generated or cause downtime if your origin is unresponsive, so use with caution.
Available on all plans. Learn more about cache invalidation.