# Dataflow Inquiry options
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.
When search results are listed in the **Dataflow Inquiry** page, clicking on the row, the details of the selected flow will appear. The username of the user who sent the file is displayed on the card. Data Mover Smart events are fully managed in Data Watcher.
These icons may appear on cards:
*  The workflow service task that had failed was resumed, within the same workflow instance.
* An Abort and Resubmit operation was performed, which created a new instance of the workflow.
*  An error was recovered; e.g., with a Resume operation, or a Resubmit operation, or internal workflow management.
*  A fatal error occurred.
*  A business error has occurred (this requires a specific license).
## Details option
Selecting the **Details** option, the **Node Details** window will appear.
When an event occurs on the server, a specific icon appears on each node. In the figure above, the following icons are shown: when the file is uploaded in Data One, when it is renamed, and when it is deleted.
Clicking a node, the **Details** and **Trace event** tabs will be displayed.
The **Details** tab shows information about the execution of the contract.
The **Trace event** tab shows trace event information; e.g. ID, dataflow Instance ID, log Correlation Id, user who executed action, and so on.
The status of the contract is given in the **Details** tab. If the status is successful, a green bar will appear.
If the contract is in error, a red bar will appear with the reason of the failure.
To resume jobs in error when Data Watcher and Data Mover are bundled:
1. In **Data One**, go to **Monitoring → Dataflow Inquiry**.
2. Click the **3-dot icon** on the node in error.
3. Select **Details**.
4. Choose the node showing the error.
5. Locate the **JobID** entry on the right-hand side.
6. Click the  **View in Jobs** icon on the JobID line to resume the job.
7. You will be redirected to the **Jobs** page, where you can resume the job, or abort it as needed. Then, from the **Jobs** page, you can easily get back to Data Watcher by clicking the 3-dots icon and selecting **View Dataflow**.
## Events option
The **Events** option provides information about events related to file transfers (Incoming and/or Outgoing), creation (Local), purge due to retention classes (Local), physical delete (Local), and rename (Local).\
The **Timestamp**, **Event**, **Context**, and **Status** of each event are listed in the table.
Clicking each row, additional information can be found on the **Event details** and **Trace events** tabs on the right.
The **Event details** window lists information about the transfer, such as protocol, mode, virtual path and event executed, and information about the event, such as when it started and ended, the connection contract used, the partner involved, the source file name and so on. Moving to a different row, the window will be updated.
In order to enhance focus on critical tasks and reduce unnecessary data processing, specific events that should not be transmitted can be filtered in Data Watcher. This can be achieved by configuring a particular property designed to selectively prevent the forwarding of events associated with designated service tasks to Data Mover and Watcher. See the [Filter events](/data-mover-1.21/how-to.../...-fine-tune-data-mover-with-advanced-settings/filter-events.md) page for details.
The **Trace events** window lists trace fields. They can be filtered with the **Search** bar at the top of the window. Just enter a portion of the field you want to see and it will be filtered accordingly. When you move to a different row, the filter will be applied to the new event. To remove it, just click the X button. \
Among **Trace event** fields, there is the name of the remote user (UserName) who has executed the action. This is particularly useful to see which user performed rename and delete operations.
---
# 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/dataflow-inquiry-options.md?ask=
```
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.