> For the complete documentation index, see [llms.txt](https://docs.does.qa/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.does.qa/runs/run-history-and-detail.md).

# Run History and Run detail

**Runs** in the main menu opens **Run History**. That list is the account-wide view of Runs. A Flow’s **Results** tab shows Runs for that Flow only.

![Passed Run detail with Flow summary](/files/VQWTzefLNPxUKptNjGUW)

## Run History

Each row shows the trigger, Run ID, counts for Flows and Tests, how many passed, status, duration, and time saved. Open a row to see the Run detail.

Use search and **Reload** when you need to find or refresh a recent Run.

## Run detail

The Run detail lists every Flow in the Run. Expand a Flow to see its Test Cases, then open a Test Case for the step timeline, screenshots, and video.

From the Run menu you can:

| Action                         | Use it to                                                                                                                         |
| ------------------------------ | --------------------------------------------------------------------------------------------------------------------------------- |
| **Reload**                     | Refresh the Run                                                                                                                   |
| **Print**                      | Print the Run view                                                                                                                |
| **Terminate Run**              | Stop a Run that is still in progress                                                                                              |
| **Run Changed & Failed Tests** | Start a follow-up Run for changed and failed Test Cases (when the Run has finished and failed, been rejected, or been terminated) |

Follow-up Runs started this way appear linked to the original. Their label often ends with `- Rerun`.

## What a rerun keeps

**Run Changed & Failed Tests** starts a follow-up Run from the original. It reuses the Values and related Run settings that were resolved when that original Run started, including account Values, Recipe overwrites, and any Value Overwrites passed into the first Run.

That keeps Recipes and CI/CD hooks stable when you retry. Updating a Value under **Assets → Values** after the original Run finished does not change what the rerun uses.

To pick up the latest Values (or new overwrites), start a fresh Run instead: run the Flow, Test Pack, Recipe, Schedule, or CI/CD hook again. See [Start a Run](/runs/start-a-run.md) and [Value Store](/values/value-store.md).

{% hint style="info" %}
**Pro tip:** Use a rerun when you want the same inputs as the first attempt. Use a new Run when you have changed Values or filters and need those changes applied.
{% endhint %}

## Statuses you will see

| Status          | Meaning                                             |
| --------------- | --------------------------------------------------- |
| Queued          | Waiting to start                                    |
| Creating Runner | Preparing the browser environment                   |
| Running         | Test Cases are in progress                          |
| Passed          | Finished successfully                               |
| Failed          | At least one Test Case failed                       |
| Rejected        | The Run did not complete successfully               |
| Terminated      | Someone stopped the Run                             |
| Preview         | Created by **Preview Tests**, not a normal live Run |

While a Test Case runs, you can open it for live progress. When it finishes, review failing steps first. Getting Started covers that path in [Understand your results](/getting-started/understand-your-results.md).

{% hint style="info" %}
**Pro tip:** Prefer **Run History** when you started a Test Pack, Recipe, Schedule, or CI/CD Run across many Flows. Prefer the Flow **Results** tab when you are iterating on one Flow.
{% endhint %}

## Related

* [Runs](/runs/runs.md)
* [Start a Run](/runs/start-a-run.md)
* [Value Store](/values/value-store.md)
* [Understand your results](/getting-started/understand-your-results.md)
* [Notifications](/configuration/notifications.md)
* [Max Concurrency](/configuration/max-concurrency.md)