> For the complete documentation index, see [llms.txt](https://docs.avoautomation.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.avoautomation.com/avo-assure/create-and-execute-tests-with-design-studio/working-with-reports-section/features-in-report-section-1/re-run-failed-test-cases/re-run-the-failed-test-cases.md).

# Re-running the Failed Test Cases

To Re-run the failed Test Cases in Avo Assure we have two ways

* [**Reports Tab**](#re-run-failed-test-case-from-reports-tab)
* [**Execution Tab**](#re-run-failed-test-case-from-execution-tab)

### **Re-Running Failed Test Case from Reports Tab**

1. Navigate to **Reports tab** and click on **Re-Run Test Case** option beside the Test Case Summary column, the failed test case pop-up will appear

<figure><img src="https://2174257472-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fk8QZzXZMIJSStKAzDSTu%2Fuploads%2F3HczqFoZofUNNbm0yz71%2Fimage.png?alt=media&amp;token=833654cd-38e0-47f5-a83d-8ee611c57646" alt=""><figcaption></figcaption></figure>

2. Select **Failed Test Case** from the table which needs to execute again and Click on **Re-Run** button

<figure><img src="https://2174257472-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fk8QZzXZMIJSStKAzDSTu%2Fuploads%2FZN4Fayld0ojszwH3IGsz%2Fimage.png?alt=media&amp;token=c7d29d20-b9e6-495a-aa9b-a284991ab34b" alt=""><figcaption></figcaption></figure>

3. The Execution Now pop-up appears. Select the desired options and enable the **Re-Run Failed Test Case** toggle button located below, and set the **Re-run Count** (any value between 1 to 5)

<figure><img src="https://2174257472-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fk8QZzXZMIJSStKAzDSTu%2Fuploads%2FSnfpQhaVm2uzvpCq4f4L%2Fimage.png?alt=media&amp;token=4ece5365-dae1-4c75-92f0-e9b10315f0cd" alt=""><figcaption></figcaption></figure>

4. Click on **Execute** button

<figure><img src="https://2174257472-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fk8QZzXZMIJSStKAzDSTu%2Fuploads%2FWvrHalr5606lROhOJKTf%2Fimage.png?alt=media&amp;token=b1655c16-9f62-437a-a111-dcd766f879da" alt=""><figcaption></figcaption></figure>

### **Re-running Failed Test Case from Execution Tab**

Navigate to Execution on Client page then click below link\
[Execution on Client](/avo-assure/create-and-execute-tests-with-design-studio/working-with-execution-section/execute-execution-list/execution-through-client-agent-grid.md)

### Example

**Let’s say a test execution gave the following results:**

| **Test Case**          | **Result** |
| ---------------------- | ---------- |
| TC\_01 (Fund Transfer) | Failed     |
| TC\_02 (Loans)         | Passed     |

The **Re-run Failed Test Cases** option is enabled, and the rerun count is set to 3.

* Only **TC\_01 (Fund Transfer)** will be rerun because **TC\_02 (Loans)** already passed.
* If **TC\_01 (Fund Transfer)** continues to fail, it will be retried up to 3 times.
* The final report will show the latest result of **TC\_01 (Fund Transfer)** after the reruns.


---

# 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.avoautomation.com/avo-assure/create-and-execute-tests-with-design-studio/working-with-reports-section/features-in-report-section-1/re-run-failed-test-cases/re-run-the-failed-test-cases.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.