> For the complete documentation index, see [llms.txt](https://clients.medianova.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://clients.medianova.com/products/performance-cdn/dynamic-content-acceleration/advanced-configuration/purge.md).

# Purge

Instantly invalidate outdated cache entries across all Medianova CDN cache layers to ensure the latest content is delivered globally without waiting for TTL expiration.

The **Purge** feature for **Dynamic Content Acceleration** works the same way as for **Static Content Delivery**.\
It allows you to **instantly invalidate cached content** across all Medianova CDN cache layers, ensuring that users always receive the most recent version of your dynamic assets.

Purge operations remove outdated or modified files from CDN cache and trigger fresh retrieval from your origin upon the next request.\
This guarantees consistency and fast propagation across all edge and shield locations.

For detailed usage steps, behavior, and best practices, please visit the main Purge documentation below:

**Learn all about** [**Purge**](/products/performance-cdn/static-content-delivery/advanced-configuration/purge.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://clients.medianova.com/products/performance-cdn/dynamic-content-acceleration/advanced-configuration/purge.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.