Problem Statement:

When an article, redirect rule, or custom domain change is published, the edge cache can take up to several minutes to refresh. During this window, readers may see a 404 error or stale content. The only current workaround is a query-parameter bypass, which only affects the individual visitor's own request; it does not clear the cache for other readers, so the underlying delay for the broader audience remains unresolved. There is no way for an author to force an immediate cache refresh for all visitors after a time-sensitive publish.

Suggested Enhancement:

Add a "Purge cache" action in the Knowledge base portal (available at the article level and/or site level) that lets authors manually invalidate the cached version of specific content immediately after publishing, rather than waiting for the automatic expiry window.

Customer Benefit:

Reduces reader-facing 404 errors and stale-content sightings after urgent publishes, redirect changes, or custom domain updates, and removes the need for authors to communicate "please wait a few minutes" workarounds to their audience.