> For the complete documentation index, see [llms.txt](https://docs.catalyx.solutions/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.catalyx.solutions/catalyx-blockchain-manager/canton-network/version-2.0/console-guide-canton/validators/overview/status.md).

# Status

The **Status** page displays the live condition stream from the CAT-BM Operator for this validator. It is the primary place to diagnose why a validator is not in a Ready state.

<div data-with-frame="true"><figure><img src="/files/sIBZ3GPGdpXDsXlA98E0" alt=""><figcaption></figcaption></figure></div>

***

### Status Cards

Three summary cards are shown at the top of the page:

| Card                    | Description                                                                        |
| ----------------------- | ---------------------------------------------------------------------------------- |
| **Database**            | Whether the validator's database has been provisioned (e.g. `Provisioned`).        |
| **Auth provisioned**    | Whether the authentication configuration has been provisioned (e.g. `Yes`).        |
| **Observed generation** | The resource generation number that the Operator most recently reconciled against. |

The **Observed generation** value increments each time the Validator CR spec is updated. If the observed generation does not match the current resource version, the Operator may still be reconciling a recent change.

***

### Conditions Table

Below the status cards, a table lists all conditions reported by the validator controller:

| Column              | Description                                                                          |
| ------------------- | ------------------------------------------------------------------------------------ |
| **Type**            | The condition type (e.g. `Ready`).                                                   |
| **Status**          | Whether the condition is currently true or false.                                    |
| **Reason**          | A machine-readable reason code for the current status (e.g. `AllApplicationsReady`). |
| **Message**         | A human-readable description of the current state.                                   |
| **Last transition** | The timestamp of the most recent status change for this condition.                   |

{% hint style="info" %}
Non-Ready states should be acted on. If the **Ready** condition shows `False`, check the **Reason** and **Message** columns for details, and refer to the [Summary](/catalyx-blockchain-manager/canton-network/version-2.0/console-guide-canton/validators/overview/summary.md) page to identify which component is unhealthy.
{% endhint %}

{% hint style="info" %}
\[TODO: document the full set of condition types and reason codes that can appear — e.g. conditions other than Ready, and non-AllApplicationsReady reason codes]
{% endhint %}


---

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

```
GET https://docs.catalyx.solutions/catalyx-blockchain-manager/canton-network/version-2.0/console-guide-canton/validators/overview/status.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.