> For the complete documentation index, see [llms.txt](https://docs.pentaho.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pentaho.com/pdc-10.2-data-optimizer/pdso-management/pdso-data-operations.md).
# Data Operations
You can monitor, verify, and examine details about your past, current, and pending data operations on the Data Operations page. Information about tiering, purging, and rehydration operations can be used to manage your files. You can filter operations using the **Completed** and **Failed** buttons. In addition, you can enter folder and file names in **Search** to search the Data Operations page for the results of the operations.
Click **Submitted**, **Completed**, or **Failed** on the **Data Operations** card to open the Data Operations page.
The tabular information shown on the Data Operations page is described below.
| Column | Description |
| ----------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| 
| **More options** icon. Click **More options** and choose **Rehydration** to rehydrate a file. See [Rehydration](/pdc-10.2-data-optimizer/pdso-management/pdso-rehydration.md). |
| **Name** | Name of the file. |
| **Path** | Path of the file. |
| **Source** | The source of the file. |
| **Type** | The action performed or scheduled. |
| Icon | Definition |
| 
| File tiered. |
| 
| File purged. |
| 
| File rehydrated. |
| **Destination** | The destination of the file. |
| **Source Type** | The source type of the file. See [Data sources](/pdc-10.2-data-optimizer/pdso-management/pdso-data-sources.md). |
| **Destination Type** | The data target type for the tiered or rehydrated file. |
| **Status** | The status of the data operation: - SUCCESS
- INIT (Initializing)
- FAILED
|
| **Tag** | The tag applied to the file. |
| **Action** | The method used to initiate the operation:- UI
|
| **File Format** | The file format of data. |
| **Size** | The size of the file. |
| **Message** | The message returned about the data operation by Data Optimizer. |
| **Started** | Time the operation began. |
| **Ended** | Time the operation ended. |
| **Time taken** | Total time taken for the operation. |
You can use the Data Operations page to understand the results of your data operations. Click \*\*Completed\*\* to sort the data according to completed operations. Click \*\*Failed\*\* to sort the data according to failed operations.
You can perform the following tasks:
* [Viewing data operations](/pdc-10.2-data-optimizer/pdso-management/pdso-data-operations/pdso-view-data-operations.md)
* [Tiering workflow](/pdc-10.2-data-optimizer/pdso-use-data-storage-optimizer/pdso-workflows/pdso-tiering-workflow.md)
* [Purging workflow](/pdc-10.2-data-optimizer/pdso-use-data-storage-optimizer/pdso-workflows/pdso-purging-workflow.md)
* [Rehydration](/pdc-10.2-data-optimizer/pdso-management/pdso-rehydration.md)
---
# 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.pentaho.com/pdc-10.2-data-optimizer/pdso-management/pdso-data-operations.md?ask=&goal=
```
`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.