> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/xsoar-6-administrator-guide/6.15/onboard-cortex-xsoar/marketplace/content-pack-installation/revert-a-content-pack.md).

# Revert a Content Pack

Revert a Cortex XSOAR 6.15 content pack to an earlier version.

You can revert an installed content pack to an earlier version.

{% hint style="info" %}

### Note

If you roll back to an earlier version of a content pack, other content packs might be affected. For example, if content pack A depends on layouts from content pack B Version 2, reverting to content pack B Version 1 could cause content pack A to stop working.
{% endhint %}

1. In the **INSTALLED CONTENT PACKS** tab of the Marketplace, search for the content pack.
2. In the **Version History** tab of the content pack, view the previous versions.
3. Choose the version you want to revert to and click **Revert to this version**. The version will be added to your cart.
4. In the Marketplace cart, click **Downgrade**.


---

# 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 dynamically by asking a question.

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

```
GET https://cortex-docs.paloaltonetworks.com/xsoar-6-administrator-guide/6.15/onboard-cortex-xsoar/marketplace/content-pack-installation/revert-a-content-pack.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 `build a script that syncs our docs to a CMS` 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.