> For the complete documentation index, see [llms.txt](https://docs.umbraco.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.umbraco.com/umbraco-cms/17.latest/develop-with-umbraco/application-code/examine/corrupt-indexes.md).

# Corrupt Indexes

The data integrity of Examine index files can be compromised if for example files are removed. When this happens, Umbraco considers the index to be corrupt.

As some systems are already hooked into the Examine index lifecycle, resolving this issue outside the application is safest.

## Resolution in a self-hosted environment

The following steps cover clearing out corrupt indexes in a self-hosted environment.

1. Stop the website/app pool.
2. Remove the directory containing the corrupted index files.
3. Restart the website.

## Resolution on Umbraco Cloud

The following steps cover clearing out corrupt indexes in a setup hosted on Umbraco Cloud.

1. Open the project in the Cloud Portal.
2. Select the correct environment.
3. Access KUDU.
4. Open the debug console.
5. Choose CMD.
6. Navigate to `C:\home\site\wwwroot\umbraco\Data\Temp`.\
   7- Click the delete button next to the index file.
7. Restart the environment.


---

# 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.umbraco.com/umbraco-cms/17.latest/develop-with-umbraco/application-code/examine/corrupt-indexes.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.