> 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.10/configure-cortex-xsoar/incident-configuration/configure-incident-export-and-delete/schedule-incident-export-and-delete.md).
# Schedule incident export and delete
Schedule incident exports and deletions to external storage in Cortex XSOAR 8.10 On-prem.
Schedule incident export, deletion, or both in Cortex XSOAR 8.10 On-prem. Scheduled exports store incident data in configured external storage. You can delete incidents only, or delete them after export.
### Before you begin
{% hint style="warning" %}
To export incidents, first configure an external storage solution. See [Configure access to external storage](/cortex-xsoar-8-on-prem/8.10/configure-cortex-xsoar/incident-configuration/configure-incident-export-and-delete/configure-access-to-external-storage.md).
{% endhint %}
{% hint style="info" %}
* The first time incidents are exported, the process may take multiple days or weeks, depending on the number of incidents and the amount of data. The system must complete the previous export before starting another.
* To stop an existing export process, click the **Abort** button. The **Abort** button appears only when an export is in progress.
* If an export fails, the Instance Admin receives an email notification. To enable or disable notification settings, click on your username and select **User Preferences** → **Notifications** → **Other Notifications** → **Scheduled export and delete failure**.
* Once an incident has been exported, it is not exported again, even if it remains in the system and is modified after the export.
{% endhint %}
After you enable scheduling, the **Export and Delete Incidents** page shows the next scheduled procedure. It also shows the last successful procedure. During an active procedure, it shows the current status.
### Schedule incident actions
Schedule an incident export
1. Go to **Settings & Info** → **Settings** → **System** → **Export Incidents**.
2. Toggle the button to **Enable scheduled exports**.
3. Select **Export**.
4. Select the time range. For example, if you select three months, all incidents created more than three months ago are exported. The minimum value is one month.
5. Select whether to **Include incident attachments**.
6. Choose the frequency, days, and time.
7. Choose an existing external storage option.
8. Enter the relative storage path. For example, for the `export_incidents` folder in an Amazon S3 bucket, enter `export_incidents`.
9. **Save**.
Schedule incident deletion
1. Go to **Settings & Info** → **Settings** → **System** → **Export Incidents**.
2. Toggle the button to **Enable scheduled exports**.
3. Select **Delete**.
4. Select the time range. For example, if you select three months, all incidents created more than three months ago are deleted. The minimum value is one month.
5. Choose the frequency, days, and time.
6. **Save**.
Schedule incident export and deletion
If you choose to export and then delete incidents, no incident is deleted until it has been exported.
1. Go to **Settings & Info** → **Settings** → **System** → **Export Incidents**.
2. Toggle the button to **Enable scheduled exports**.
3. Select **Export then delete**.
4. Select the time range. For example, if you select three months, all incidents created more than three months ago are exported and then deleted. The minimum value is one month.
5. Select whether to **Include incident attachments**.
6. Choose the frequency, days, and time.
7. Choose an existing external storage option.
8. Enter the relative storage path. For example, for the `export_incidents` folder in an Amazon S3 bucket, enter `export_incidents`.
9. **Save**.
---
# 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://cortex-docs.paloaltonetworks.com/cortex-xsoar-8-on-prem/8.10/configure-cortex-xsoar/incident-configuration/configure-incident-export-and-delete/schedule-incident-export-and-delete.md?ask=&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.