> For the complete documentation index, see [llms.txt](https://help.docupilot.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.docupilot.app/workflows/workflow-runs.md).

# Workflow Runs

A workflow run records one execution of a workflow. Runs let you confirm what happened after a form submission, API request, or test.

## View Workflow Runs

1. Open a workflow.
2. Select **Workflow runs**.
3. Filter by status, run type, or date range, or search by run ID.
4. Select a run to open its execution view.

Use **Live runs** for real submissions and **Test runs** for executions started with Test Run.

## Workflow Run Statuses

* **Queued**: The run has been accepted and is waiting to start.
* **Running**: One or more modules are being processed.
* **Waiting**: Execution is temporarily waiting before it can continue.
* **Completed**: All modules on the selected path completed successfully.
* **Failed**: A module encountered an error that stopped its dependent path.
* **Cancelled**: The run was stopped before completion.

## Inspect a Run

The canvas highlights the path taken by the selected run. Select an executed module to review:

* module execution status
* input data received by the module
* output data produced by the module
* error details, when applicable

The submitted form values appear with the run and in the Form module's data. The run also records the workflow version used for that submission.

Modules can appear as skipped or blocked when their condition branch was not selected or a required upstream module failed. Independent branches can continue even when another branch fails.

## Investigate a Failed Run

1. Open the failed run.
2. Find the failed module on the canvas.
3. Select the module and read its error message.
4. Review its input data and the output from upstream modules.
5. Correct the workflow configuration or submitted data.
6. Save and test the updated draft.

When contacting support, include the workflow name, workflow version, run ID, failed module, and complete error message.


---

# 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://help.docupilot.app/workflows/workflow-runs.md?ask=<question>&goal=<endgoal>
```

`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.