> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/cortex-xdr-5.x/protect-your-endpoints/install-and-manage-endpoints/manage-endpoint-protection/monitor-agent-upgrade-status.md).

# Monitor agent upgrade status

From Cortex XDR, you have full visibility into the Cortex XDR agent upgrade status on the endpoint. You can monitor the Cortex XDR agent statuses in **Inventory** → **Endpoints** → **All** **Endpoints**. If the upgrade status fields are missing, add them.

### Cortex XDR agents report upgrade statuses as follows:

| **Status**                      | **Description**                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
| ------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Last upgrade status**         | <p>Displays the last upgrade status for each endpoint, and can be filtered by:<br></p><ul><li><strong>In Progress:</strong> This is the first stage shown when an upgrade is initiated (There is no Pending status).</li><li><strong>Completed Successfully</strong></li><li><strong>Failed</strong></li><li><strong>No Upgrade:</strong> No upgrade of any type has been initiated for the endpoint. Newly installed endpoints will also show this status until an upgrade is initiated by one of the upgrade methods.</li></ul> |
| **Last upgrade status time**    | Displays a timestamp for the last time the upgrade status changed for each endpoint. This column can be filtered by date and time.                                                                                                                                                                                                                                                                                                                                                                                                |
| **Last upgrade failure reason** | When relevant, displays the reason for an upgrade failure. This column can be filtered by free text.                                                                                                                                                                                                                                                                                                                                                                                                                              |
| **Last upgrade source**         | <p>Displays the source that initiated the last upgrade, and can be filtered by:<br></p><ul><li><strong>Manual Server Upgrade:</strong> The upgrade was manually initiated from the server.</li><li><strong>Auto Upgrade:</strong> The endpoint was automatically upgraded according to the upgrade policy.</li><li><strong>Local Manual Upgrade:</strong> The upgrade was manually initiated at the endpoint side.</li></ul>                                                                                                      |


---

# 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://cortex-docs.paloaltonetworks.com/cortex-xdr-5.x/protect-your-endpoints/install-and-manage-endpoints/manage-endpoint-protection/monitor-agent-upgrade-status.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.