> For the complete documentation index, see [llms.txt](https://docs.antsomi.com/cdp-365-user-guide-en/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.antsomi.com/cdp-365-user-guide-en/data-hub/business-objects/export-histories.md).
# Export Histories
The system will record every time you download a file in the Export Histories section. After 6 months since the end date of the downloading process, the files will be deleted from the system and users could not download it. The status of these files is **Expired**.
Hover your mouse over **Settings**. Under **Histories**, choose **Export**.
## Export Histories Information
Export Histories shows a data table:
* **Export ID**: ID of export
* **Export file**: The full name of the file that you used to export
* **Export status**: Status of the export process (In Process, Done, Failed)
* **Object:** The name of the object whose data table is being exported
* **Exported rows**: Number of rows of the exported file
* **Export started on**: Export start date and time
* **Export ended on**: Export end date and time
* **Export duration (sec)**: Export processing time (in seconds)
* **Exported by**: Account who exported the data
* **Fail info**: Information about the reason for the failed export
## Downloading an exported file
CDP 365 allows you to download an exported file by hovering and clicking  on the Exported file row and receiving the result
{% hint style="warning" %}
Note: You can only download an exported file when its status is done
{% 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://docs.antsomi.com/cdp-365-user-guide-en/data-hub/business-objects/export-histories.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.
