> 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/deleting-recovery-steps.md).

# Deleting Recovery Steps

This section explains how to delete **Recovery steps** from the **Test Case** page. It describes how to remove created recovery steps when they are no longer required for test execution.

In the **Test Case** page, we can delete created recovery steps at three levels.

1. Folder Level
2. Sub Folder Level
3. Test case Level

## Deleting Folder Level Recovery Steps

To delete created **Recovery steps** at the Folder level in the **Test Case** page, perform the following actions:

1. On the **Home** page, under **Projects**, select the required **Project**.
2. Select **Design Studio** and select the **Test Case** page.
3. In the **Test Case** page, locate the parent folder.
4. Select the parent folder, select the **Recovery steps**.
5. Select the **Delete Recovery step** icon.

<figure><img src="/files/m16kWAgyUd6blYE4roG8" alt=""><figcaption></figcaption></figure>

6. From the **Confirmation** dialog, select the **Yes** button to delete the created Recovery steps.

<figure><img src="/files/8MuPUYvksZnk40V8y7e3" alt=""><figcaption></figcaption></figure>

## Deleting Sub Folder Level Recovery Steps

To delete created **Recovery steps** at the sub folder level in the **Test Case** page, perform the following actions:

1. On the **Home** page, under **Projects**, select the required **Project**.
2. Select **Design Studio** and select the **Test Case** page.
3. In the **Test Case** page, locate the parent folder.
4. From the parent folder, select the **Expand** arrow icon. A sub folder displays.
5. Under the sub folder, locate the **Recovery steps**.
6. Select the **Recovery steps** and select the **Delete Recovery step** icon.

<figure><img src="/files/m0rbjnnTmQFeukGiKt9i" alt=""><figcaption></figcaption></figure>

7. From the **Confirmation** dialog, select the **Yes** button to delete the created Recovery steps.

<figure><img src="/files/1EeD8SburuX1tDGqSasG" alt=""><figcaption></figcaption></figure>

## Deleting Test case Level Recovery Steps

To delete created **Recovery steps** at the Test case level in the **Test Case** page, perform the following actions:

1. The initial setup for the Test case level follows the same process as the sub folder level (Steps 1–4). After completing those steps, you can delete the create recovery steps at the Test case level as described below.
2. From the sub folder, select the **Expand** arrow icon. Test cases are displayed.
3. Under the Test case, locate the **Recovery steps**.
4. Select the **Recovery steps** and select the **Delete Recovery step** icon.

<figure><img src="/files/S3RyuIWSqSb7Z2KtLopK" alt=""><figcaption></figcaption></figure>

5. From the **Confirmation** dialog box, select the **Yes** button to delete the created Recovery steps.

<figure><img src="/files/UniM5mfyVw7oz2Dkxoak" alt=""><figcaption></figcaption></figure>


---

# 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/deleting-recovery-steps.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.
