> 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/guides/operations/upgrades-and-releases/status-signals.md).

# Status signals

Where each upgrade surface reports progress - cluster status and Activity History, product rows, and the Platform Components section.

Each upgrade surface reports progress in its own way. Use this page to know where to look while an upgrade runs.

## Where each surface reports

| Surface         | Where to look                                          | Signals                                                                                                                     |
| --------------- | ------------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------- |
| Cluster         | Cluster status + the **Activity History** panel        | Operation type (Create / Update / Suspend / Resume), status (In Progress / Success / Failed / Preempted), and error details |
| Product upgrade | The **Version Upgrades** row status                    | Upgrading… → Ready/Running, or Failed, with a completion notification                                                       |
| Platform        | The **Platform Components** section status and banners | Deploying → Deployed, or Failed / Rolled Back with per-component detail                                                     |

## Activity History (clusters)

The Activity History panel records each operation on a cluster and, when something fails, shows the error with a severity level, the component involved, and a recommended action. Use it as the first stop when diagnosing a cluster upgrade that didn't go as expected.

## See also

* [Rollbacks, failure modes, and recovery](/query-engine/guides/operations/upgrades-and-releases/rollbacks-failure-modes-recovery.md) - how to act on a failed or rolled-back status.
* [Product and cluster upgrades](/query-engine/guides/operations/upgrades-and-releases/product-and-cluster-upgrades.md) - triggering the upgrades these signals track.


---

# 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/guides/operations/upgrades-and-releases/status-signals.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.