> For the complete documentation index, see [llms.txt](https://docs.testvibe.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.testvibe.com/run-tests/cancel-or-rerun-tests.md).

# Cancel or Re-run Tests

You can cancel an active run when it is no longer useful, and you can re-run a previous run when you want a fresh result for the same selection.

## Cancel an active run

Cancel a run when:

| Situation                             | Why cancel                                              |
| ------------------------------------- | ------------------------------------------------------- |
| The wrong site URL was entered        | The result will not represent the intended environment. |
| The wrong tests were selected         | The run is spending time on the wrong scope.            |
| A required service is down            | Failures would only confirm an external outage.         |
| A newer change makes the run obsolete | A fresh run will give a better signal.                  |

To cancel:

1. Open **Runs**.
2. Select the active run.
3. Choose **Cancel**.
4. Confirm the action if TestVibe asks for confirmation.

The run moves to a cancelled state. Any partial evidence that was already produced may still be visible, but the run should not be treated as a pass or failure signal.

## Re-run a previous run

Re-run when you want to retry the same test selection after fixing a problem, updating the target site, or refreshing credentials.

1. Open **Runs**.
2. Select the completed, failed, or cancelled run.
3. Choose **Re-run**. The run composer opens pre-scoped to that run: the same tests are pre-checked and the same Playwright configurations are pre-selected.
4. Adjust the selection if needed — add or remove tests, or switch configurations.
5. Choose **Start Run**. The new run targets the same site URL as the run you are re-running.

![The run composer opened by Re-run, pre-scoped to the previous run](/files/fGdF2Wtw9quycXFTmjNH)

Choosing **Re-run** does not start anything by itself — the new run is only dispatched when you choose **Start Run**, so it is safe to open the composer just to review what a previous run covered.

A re-run creates a new run attempt. The original run remains available in the history so you can compare the before and after results.

## What carries forward

The composer opens pre-filled from the previous run:

| Item              | How it is pre-filled                                                     | What to check                                                                                  |
| ----------------- | ------------------------------------------------------------------------ | ---------------------------------------------------------------------------------------------- |
| Test selection    | The run's tests are pre-checked.                                         | Confirm the same files or group are still the right scope, or narrow to just the failed tests. |
| Site URL          | The previous run's target URL is reused, including any override it used. | To target a different environment, start a fresh run with **New Run** instead.                 |
| Run configuration | The run's Playwright configurations are pre-selected.                    | Confirm browser, viewport, and evidence settings.                                              |
| Secrets           | Read from **Settings → Variables & Secrets** at run time.                | Refresh credentials if the earlier failure was caused by authentication.                       |

## Delete old results

Some completed run rows can also be deleted from the run list. Deleting a result removes that historical run from the TestVibe view. Cancel first only when a run is still active; delete only when you no longer need the historical result.

For status meanings, see [Understand live run status](/run-tests/understand-live-run-status.md).


---

# 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://docs.testvibe.com/run-tests/cancel-or-rerun-tests.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.