> For the complete documentation index, see [llms.txt](https://docs.cloudio.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cloudio.io/working-with-patches/working-with-patches/deleting-a-patch.md).

# Deleting patches

To delete all the patches,

1. On the upper right corner of the CloudIO homepage, click ![](/files/-M-mqQrhvyhl1QdlDK3f) . The **Navigation** page is displayed.

![](/files/-M-s2XPucnvcwYPsktqv)

 2\. Under **Patch Manager**, click **Manage Patches**. The patch downloads/uploads page is displayed.

![](/files/-M-t5f_MWMHvNkJrzFzh)

{% hint style="info" %}
**Note**: You can delete the patches that are available for download as well as the uploaded ones.
{% endhint %}

 3\. In the **Download** page, in the upper right corner, click **Purge**. The **Purge** window is displayed.

![](/files/-M-t70-td9Kq1yRfhnFU)

 4\. In the **Purge Before** calendar**,** select the the data before which you want the patches deleted and click **Submit**. The patches are deleted.


---

# 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 current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.cloudio.io/working-with-patches/working-with-patches/deleting-a-patch.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.