> 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-saas/investigate-and-respond-to-threats/incidents-and-indicators-investigation/incident-management/export-incidents/export-incidents-on-demand.md).

# Export incidents on demand

Export Cortex XSOAR 8 SaaS incidents to cloud storage on demand.

You can export incidents on demand, choosing all incidents older than a specified time range.

{% hint style="warning" %}
Before exporting incidents, you must configure an external cloud storage solution. For more information, see [Configure access to external storage](/cortex-xsoar-8-saas/configure-cortex-xsoar/incident-configuration/export-cortex-xsoar-incidents-to-cloud-storage/configure-access-to-external-storage.md)
{% endhint %}

{% hint style="info" %}

* The **Export Now** button is only enabled if there is no active export in progress. You cannot run multiple exports at the same time.
* You can only export incidents that are older than one month.
* 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 previous export must be completed before the system begins another export.
  {% endhint %}

1. Go to **Settings & Info** → **Settings** → **System** → **Export Incidents**.
2. Click **Export Now**.
3. Choose an existing external storage option from the dropdown.
4. Enter the relative path where the data is stored. For example, if the data is stored in the `export_incidents` top-level folder in an Amazon S3 bucket, the relative path is `export_incidents`.
5. Select the time range for incident export. For example, if you select three months, all incidents created more than three months ago are exported. The minimum value is one month.
6. Select whether to **Include incident attachments**.
7. **Export**.

{% hint style="info" %}

* To stop an existing export process, click the **Abort** button. The **Abort** button only appears when an export is in process.
* 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 %}


---

# 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-saas/investigate-and-respond-to-threats/incidents-and-indicators-investigation/incident-management/export-incidents/export-incidents-on-demand.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.