> For the complete documentation index, see [llms.txt](https://docs.mozark.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mozark.ai/test-context-manager-documentation/test-runs/creating-a-test-run/executing-a-test-case/retrying-a-test-case.md).

# Retrying a test case

Re-run a failed test case without creating a new test run.

## Retrying a test case

If a test case fails, you can retry it without creating a new test run.

To add a retry:

1. Open the execution page.
2. Find the **Run Attempts** section.
3. Click **Add Retry**.
4. Select the device and configuration for the retry.
5. Execute the steps again.
6. Record the result for each step.

The retry can use a different device or configuration from the original attempt.

Test Context Manager supports up to three retries per test case per run.

Attempt labels include:

* `Run-1`
* `Retry-1`
* `Retry-2`
* `Retry-3`

All attempts remain visible in **All Runs Summary**.


---

# 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.mozark.ai/test-context-manager-documentation/test-runs/creating-a-test-run/executing-a-test-case/retrying-a-test-case.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.