> 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/develop-with-umbraco/application-code/examine/corrupt-indexes.md).

# Corrupt Indexes

How to deal with Corrupt Examine 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.umbraco.com/umbraco-cms/develop-with-umbraco/application-code/examine/corrupt-indexes.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.