> For the complete documentation index, see [llms.txt](https://docs.omics.ai/products/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.omics.ai/products/workbench/instruments/monitor-the-workflow.md).

# Monitor the Workflow

The Monitor page provides an up-to-date status on submitted runs. Click into a Workflow run to view a comprehensive overview of the run-time details, inputs, outputs and logs.

### **Viewing All Workflow Runs**

1. Navigate to the **Monitor** tab to see a list of all submitted workflow runs.
2. The list displays:
   * **Status** (e.g., Succeeded, Failed, Aborted).
   * **Submitted Date** and **Run Time**.
   * **Workflow Name**, **Version**, **Engine**, and **Run ID**.
   * Associated **Batch ID** and **Sample**.

### **Viewing Workflow Details**

1. Click on a specific run in the list to view its **Overview**. The tab shows the following:
   * **Run ID**.
   * **Workflow Name** and **Version**.
   * **Start Time**, **End Time**, and **Elapsed Time**.

### **Reviewing Workflow Inputs**

1. Click on the Inputs tab.
2. View the JSON tree of inputs used for the workflow.
   * For Instrument-enabled workflows, all inputs are auto-generated, simplifying the process.

### **Reviewing Workflow Outputs**

1. Click on the **Outputs** tab.
2. View the JSON tree of outputs generated by the workflow.

### Summary

The Instruments feature in Workbench provides an efficient, user-friendly way to connect storage, manage samples, and execute workflows. By leveraging the UI, users can perform complex genomic analyses without needing advanced technical expertise.


---

# 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.omics.ai/products/workbench/instruments/monitor-the-workflow.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.