> 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/cortex-xsoar-8-on-prem/8.14/configure-cortex-xsoar/incident-configuration/configure-incident-export-and-delete.md).

# Configure incident export and delete

The incident export and delete feature enables you to limit storage usage while meeting regulatory requirements for extended data retention. You can perform the following actions:

* Export incidents on demand
* Schedule automated incident export, automated incident deletion, or automated incident export and deletion

Incidents are exported as JSON files that contain the following:

* Incident data, including all incident fields
* Context data
* Investigation data
* War Room entries

In addition, you can choose to export incident attachments.

Exported incidents are sent to Amazon S3, an S3-compatible bucket, or to local NFS (Network File System) storage.

{% hint style="warning" %}

### Warning

* Deletion is permanent and deleted incidents cannot be retrieved.
* Exported incidents cannot be imported back into Cortex XSOAR.
  {% endhint %}

{% hint style="info" %}

### Note

* The first time incidents are exported, the export may take multiple days or weeks to complete, depending on the number of incidents and the amount of data. The previous export must complete before the system begins another export.
* To stop an existing export process, click the **Abort** button. The **Abort** button only appears when an export is in process.
* Once an incident has been exported, even if the incident is not deleted and remains in the system, it is not exported again. Note that this also applies to incidents that are modified after export.
* Retained incidents are not exported or deleted. For more information, see [Retain incidents](/cortex-xsoar-8-on-prem/8.14/investigate-and-respond-to-threats/incidents-and-indicators-investigation/investigate-an-incident/retain-incidents.md).
  {% endhint %}


---

# 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://cortex-docs.paloaltonetworks.com/cortex-xsoar-8-on-prem/8.14/configure-cortex-xsoar/incident-configuration/configure-incident-export-and-delete.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.