> 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/feature-and-capabilities.md).

# Understanding Re-run failed Test Case Feature and Capbilities

### Feature Purpose

In test automation, failures may occur due to various transient reasons such as:

* Temporary environmental issues (e.g., network lag)
* Backend service unavailability
* UI loading delays
* Third-party API latency

Often, these failures are not due to issues in the application under test, but rather external or random factors. This feature allows such failed test cases to be automatically retried, improving the overall pass rate without manual intervention.

### Capabilities

* Re-run of Failed Test Cases\
  Only the test cases that failed in the last execution are rerun. The passed test cases are not run again.
* Configurable Re-run Count (Up to 5 Attempts)\
  The number of times a failed test case should be retried can be set by the user. The maximum allowed reruns are 5.
* Updated Execution Report with Final Results\
  After the reruns, the execution report is updated to show the latest result of each test case.
* E2E Test Cases Treated as One Unit\
  For End-to-End (E2E) test cases, if any step fails, the entire E2E test case will be rerun as one unit.


---

# 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.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/feature-and-capabilities.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.