---
title: Index Get Doc Missing
description: Describes what AutoOps detects and surfaces with the Index Get Doc Missing insight: A high number of get-by-id requests are returning document-not-found results on one or more nodes.
url: https://docs-v3-preview.elastic.dev/elastic/autoops-insights/tree/main/elasticsearch/index_get_doc_missing
products:
  - Elastic Cloud Enterprise
  - Elastic Cloud Hosted
  - Elastic Cloud on Kubernetes
  - Elasticsearch
applies_to:
  - Elastic Cloud Hosted: Generally available
  - Elastic Cloud on Kubernetes: Generally available
  - Elastic Cloud Enterprise: Generally available
  - Self-managed Elastic deployments: Generally available
---

# Index Get Doc Missing
A high number of get-by-id requests are returning document-not-found results on one or more nodes. This often happens when applications update or fetch IDs that do not exist, or when upserts create new documents.
<note>
  For a complete list of insights, refer to [AutoOps insights](https://docs-v3-preview.elastic.dev/elastic/autoops-insights/tree/main/elasticsearch).
</note>


## Insight details


| Field     | Value         |
|-----------|---------------|
| Component | Elasticsearch |
| Severity  | High          |
| Scope     | Cluster       |
| Domains   | indexing      |


## Customization settings

You can customize these settings to adjust when AutoOps detects this event and presents the insight. Refer to [AutoOps event settings](https://docs-v3-preview.elastic.dev/elastic/docs-content/tree/main/deploy-manage/monitor/autoops/ec-autoops-event-settings) for details.
The default customization settings are:

| Setting                                                           | Type    | Default |
|-------------------------------------------------------------------|---------|---------|
| Maximum number of get doc requests for which the doc is not found | Integer | 100     |


## Example: What you might see in AutoOps

The following is an example of what you might see when this insight is triggered. Real insights use live data and links from your deployment or cluster.

### There are many index get requests that are missing documents on the following node/s: `es-data-01`


#### What was detected

There are 12 total get requests where the document is missing from the index.
The affected node/s are: `es-data-01` and `es-data-02`

#### Recommendations

<note>
  AutoOps shows different recommendations depending on how their conditions match your deployment or cluster.
</note>

<dropdown title="Check indexing operations for errors">
  **Condition**: Always shown for this insight.High `index.get.missing` counts are expected during upserts: Elasticsearch tries to fetch the document first, then creates it if missing. If updates should always target existing documents, check clients and indexing pipelines for failed or skipped index operations.
</dropdown>


#### Background and impact

Impact: A typical cause of this could be when you try to update a document by ID which does not exist. If you are carrying out upsert operations, then it will be normal for this number to increase.