> For the complete documentation index, see [llms.txt](https://docs.e6data.com/query-engine/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.e6data.com/query-engine/reference/cluster-reference/upgrade-states.md).

# Upgrade states

The states a cluster or platform upgrade moves through, and the cluster upgrade deployment phases.

Upgrades report progress differently for clusters and for platform releases.

## Cluster version upgrade

When you change a cluster's version, the cluster enters **Updating** and continues serving queries on the current version. On success it returns to **Running** on the new version; on failure it automatically reverts and returns to **Running** on the previous version, with the failure recorded in Activity History. See [Zero-downtime upgrades](/query-engine/guides/clusters/zero-downtime-upgrades.md).

For In-VPC deployments, the cluster also exposes a deployment phase: `Stable → Deploying → Switching → Draining → Cleanup → Stable` (or `RollingBack`). See [CloudPrem cluster operations](/query-engine/guides/clusters/cloudprem-cluster-operations.md).

## Platform release states

A platform release (Platform Components) progresses through:

| Status           | Meaning                                                                  |
| ---------------- | ------------------------------------------------------------------------ |
| **Not deployed** | No platform release deployed through this section yet (not an outage)    |
| **Pending**      | Selected, not yet started                                                |
| **Deploying**    | Rollout in progress                                                      |
| **Deployed**     | Successfully live                                                        |
| **Failed**       | One or more components failed                                            |
| **Rolled Back**  | The deploy failed and was automatically reverted to the previous version |

See [Rollbacks, failure modes, and recovery](/query-engine/guides/operations/upgrades-and-releases/rollbacks-failure-modes-recovery.md) and [Status signals](/query-engine/guides/operations/upgrades-and-releases/status-signals.md).

## See also

* [Cluster states](/query-engine/reference/cluster-reference/cluster-states.md)
* [Zero-downtime upgrades](/query-engine/guides/clusters/zero-downtime-upgrades.md)
* [Upgrades and releases](/query-engine/guides/operations/upgrades-and-releases.md)


---

# 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.e6data.com/query-engine/reference/cluster-reference/upgrade-states.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.