> 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-test-case-section/recovery-mechanism.md). # Recovery Mechanism The **Recovery Mechanism** in Avo Assure handles failures that occur during test execution. Test execution fails due to temporary issues such as the application freezing or becoming unresponsive, browser or network interruptions, session timeouts, or other unexpected system behavior that disrupts the test flow. When the system does not handle these failures, test execution stops or continues in an unstable state, and due to this the next Test cases may fail. This mechanism executes recovery steps when a Test case fails to ensure stable execution for subsequent Test cases. Recovery steps execute the Test case that is defined within the recovery step, and this Test case runs when the main Test case fails. By configuring recovery logic at different levels of the test structure, Avo Assure applies the defined recovery behavior based on the execution context. This approach ensures consistency during test execution. This article explains the Recovery Mechanism, how to create and delete recovery steps, and how to configure the execution list for recovery. --- # 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-test-case-section/recovery-mechanism.md?ask=&goal= ``` `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.