# Levels of detail of the dataflow

The details shown in the columns of the **Dataflow Inquiry** page, provide information about the dataflow: last event date, status, cut-offs, data (filename and file size), source and destination.

## Status column

The status of the dataflow is shown in the **Status** column of the Dataflow Inquiry page and can have one of these icons indicating the **Dataflow Integrity status**:

* ![](https://files.readme.io/bfe6b149f73c39de318f60d845b9b578d75553061dac889659283cfcc24ff0ab-image.png) Completed
* <img src="https://files.readme.io/96e93661d9d302d6f0f53ac8e8d29aa1ff3db39aed04273acb82f212f33ff66a-image.png" alt="" data-size="line"> Running
* <img src="https://files.readme.io/ffaa132b28d1a28b84078e68902c745ff439d2b4e3b1dace045b0e143476fdcb-image.png" alt="" data-size="line"> Error
* <img src="https://files.readme.io/4530472c554c3abd58adcee379322a23ac2bdf797720bb1e0668c53a01f8182d-image.png" alt="" data-size="line"> Resumable
* <img src="https://files.readme.io/306e4506a5987880a927cbd26586796623791cb354f2fc0bfd201f45c925726f-image.png" alt="" data-size="line"> Resume process submitted, waiting for new events
* ![](/files/ePJbEU1Foz0lKASn1AED)  Business error. A specific license is needed to take advantage of this feature and of its filters

🚀 A specific license is needed to take advantage of the Resume Flows feature and filter. Moreover, the user must have the **DWRESUMEDATAFLOW** permission to actually resume dataflows.

Flows can be resumed if they are monitored in a system, like Data One, in a bundle with Data Watcher.

You can use the options in the **Advanced** section of the **Filter panel** to quickly list all dataflows that can be resumed. See the **Show resumable dataflows** option in the **Filter panel** section of the [Dataflow Inquiry](/data-watcher-1.21/monitor/dataflow-inquiry.md) page.

The resume option can have a grey icon ![](https://files.readme.io/4530472c554c3abd58adcee379322a23ac2bdf797720bb1e0668c53a01f8182d-image.png) meaning that the flow can be resumed. When the icon turns yellow ![](https://files.readme.io/306e4506a5987880a927cbd26586796623791cb354f2fc0bfd201f45c925726f-image.png) the flow is waiting for new events.

To resume one or more dataflows, check the box or boxes on the left of the row and click the **Resume \<n> flows** button that appears on the left of the Search bar. After confirming that you want to resume the flows, a message will inform you that your request has been submitted. Click the **SHOW FLOWS** button if you want to list the flows that are currently being resumed. All FlowIDs will be added to the Search bar at the top of the page.

At this point, the ![](https://files.readme.io/4530472c554c3abd58adcee379322a23ac2bdf797720bb1e0668c53a01f8182d-image.png) icon can appear, meaning that the flow is still in error, or the ![](https://files.readme.io/bfe6b149f73c39de318f60d845b9b578d75553061dac889659283cfcc24ff0ab-image.png) icon can appear, meaning that the flow is completed.

## Cut-off column

The 2 icons of the **Cut-off** column show the cut-off status of the entire dataflow (upper icon) and the cut-off status of the single instance (lower icon). The icon can be one of these:

* <img src="https://files.readme.io/6cdcf6d-DW-NotSet.png" alt="" data-size="line"> No cut-off is set.
* <img src="https://files.readme.io/9d9e2789e686dab1b279a5a1565143cddacd7ad7ed9bc4163e71abb82b6863db-image.png" alt="" data-size="line"> The cut-off is **Pending**. The dataflow or the instance will be completed in the future.
* <img src="https://files.readme.io/34a9b47e31068991190eaaad4b930fc20db2cf9e5722afb4dfab2bb7178482a5-image.png" alt="" data-size="line"> The cut-off has a **Warning**. The dataflow or the instance is still pending and near the deadline.
* <img src="https://files.readme.io/4489460b4b532acf8af4a4186217dc3293b0ca9ab61cabb2c168c9df0013b7ce-image.png" alt="" data-size="line"> The cut-off is **OnSchedule**. The dataflow or the instance has been completed successfully and is on schedule.
* <img src="https://files.readme.io/5bbe41b8f3878cf715d2187861a1c05049a2ea5b0db5f624356bd06d0f284340-image.png" alt="" data-size="line"> The cut-off is in **Error**. The dataflow or the instance has not been completed or has been completed after the scheduled time.

## Additional columns

In addition to the last event date, status, cut-offs, data (filename and file size), source and destination columns, you can enable the following ones - information will be shown if applicable:

* **Model**: if the dataflow is modeled, its version will appear as a chip at the bottom of the row. This chip is shown by default. To hide it, click the <img src="/files/24Fy2Y9tFm23yArncfRn" alt="" data-size="line"> icon and uncheck the **Model** box.&#x20;
* **Attributes**: the values of the attributes assigned to the dataflow will appear as a chip at the bottom of the row. Each dataflow is modeled associating specific values. Attributes are configured by the Administrator as described on the [Configure Dataflow Attributes](/data-watcher-1.21/design/add-dataflow-attributes-to-flows.md) page.
* **Correlation ID**: the correlation ID will appear in a specific column next to the Source/Destination.

Finally, a grey chip shows whether the overflow is ignored or not: <img src="https://files.readme.io/290de24-DW-Overflow.png" alt="" data-size="line">

## Additional options

Clicking the 3 dots button on the right of the flow, the following options will appear:

* **Copy flow id**: copy the flow id to the clipboard and use it for troubleshooting.
* **Model as a flow**: open the [Dataflow Modeler](/data-watcher-1.21/model/dataflow-models.md) page.
* **New instance attribute**: configure [instance attributes](/data-watcher-1.21/design/add-dataflow-attributes-to-flows.md#dataflow-instance-attributes) that the user can select when modeling the flow.
* **Export**: download a zip file to your local drive. The zip file contains information on the events of the exported flow, which is useful for troubleshooting.
* **Resume flow** (license needed): resume the flow if monitored in a system, like Data One.
* **View in logs**: go to the [Logs](/data-mover-1.21/logs-and-audit/logs.md) page and see all the events occurred to the dataflow, filtered by its DFIID.


---

# Agent Instructions: 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:

```
GET https://docs.primeur.com/data-watcher-1.21/monitor/dataflow-inquiry/levels-of-detail-of-the-dataflow.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
