# Best Practices ### **Best Practices to use Re-Run Failed Test Cases feature in Avo Assure:** **Usage & Scope** * Use re-run mainly for failures that happen randomly (e.g., network delays or UI slowness) **Failure Analysis** * After re-runs, check the client logs to identify the actual reason for the failure **Configuration** * Avoid setting a high re-run count for test cases that consistently fail — fix the problem instead **Reliability** * Combine re-run with features like **Wait actions** and **On Failure** to improve stability in execution --- # Agent Instructions: 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: ``` GET https://docs.avoautomation.com/avo-assure/working-with-the-avo-assure-platform/create-and-execute-tests-with-design-studio/working-with-reports-section/features-in-report-section/re-run-failed-test-cases/best-practices.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.