---
title: AutoOps agent critically outdated
description: Describes what AutoOps detects and surfaces with the AutoOps agent critically outdated insight: Your AutoOps agent is behind a release that contains a required fix.
url: https://docs-v3-preview.elastic.dev/elastic/autoops-insights/tree/main/elasticsearch/autoops_agent_critically_outdated
products:
  - Elastic Cloud Enterprise
  - Elastic Cloud on Kubernetes
  - Elasticsearch
applies_to:
  - Elastic Cloud on Kubernetes: Generally available
  - Elastic Cloud Enterprise: Generally available
  - Self-managed Elastic deployments: Generally available
---

# AutoOps agent critically outdated
Your AutoOps agent is behind a release that contains a required fix. Until you upgrade it, AutoOps can receive less reliable data and other insights can become less trustworthy.
<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  | Critical                   |
| Scope     | Cluster                    |
| Domains   | stability, version-upgrade |


## 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.

### AutoOps agent 9.3.1 is missing a required update


#### What was detected

The Elastic Agent that connects this cluster to AutoOps is running 9.3.1. The recommended version is 9.3.2, and the skipped version gap includes a required fix.

#### Recommendations

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

<dropdown title="Upgrade AutoOps agent">
  **Condition**: Always shown for this insight.Upgrade the Elastic Agent that connects this cluster to AutoOps to 9.3.2 or later. Use the current installation command from [Connect your self-managed cluster to AutoOps](https://docs-v3-preview.elastic.dev/elastic/docs-content/tree/main/deploy-manage/monitor/autoops/cc-connect-self-managed-to-autoops), and apply the steps that match how you installed the agent.
</dropdown>


#### Background and impact

Cloud Connected clusters send metrics to AutoOps through a dedicated Elastic Agent that you install and operate. When that agent misses a release with a required fix, AutoOps can receive incomplete or unreliable data.
Less reliable agent collection reduces confidence in other insights and can leave cluster problems harder to spot until later.

## Guide

[Connect your ECE, ECK, or self-managed cluster to AutoOps](https://docs-v3-preview.elastic.dev/elastic/docs-content/tree/main/deploy-manage/monitor/autoops/cc-connect-self-managed-to-autoops)