> For the complete documentation index, see [llms.txt](https://docs.b2core.b2broker.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.b2core.b2broker.com/back-office-guide/system/status-checks.md). # Status checks The **Status Checks** page gives you an at-a-glance view of the health of important parts of your B2CORE instance. Each check runs automatically on a schedule and records its result, so you can spot problems, such as an unreachable trading platform or an incomplete setup, without leaving the Back Office. To open the page, go to **System** > **Status Checks** in the main menu. ## Failed checks indicator When one or more checks are failing, a warning icon appears in the topbar, next to the notifications bell, with a badge showing the number of failed checks. Click the icon to open a drop-down list of the currently failing checks. Each item shows: * The check name. * A short description of the problem. * A chip indicating how long ago the check last ran, for example, **5 minutes ago**. Select a check in the list to open the **Status Checks** page and jump to that check. {% hint style="info" %} Only checks with the **Failed** or **Error** status appear in the indicator. Checks with the **OK**, **Pending**, or **Unknown** status are not counted. {% endhint %} ## Status timeline The page lists every registered check. For each check, a horizontal timeline shows how its status changed over time, with consecutive runs of the same status grouped into a single colored period. The timeline covers up to one month. For a recently deployed instance, it starts at the first recorded run instead, so the window stays meaningful. Each check also shows: * A badge with the current status. * The time of the last run, or **never run** if there are no recorded runs yet. * The rendered details of the most recent run, for example, the list of unreachable platforms. ## Statuses A check run can have one of the following statuses. *** **OK** The check passed. The monitored area is healthy. *** **Failed** The check detected a problem, for example, a trading platform is unreachable or a required setup is missing. *** **Error** The check could not complete because of an unexpected error. The recorded details include the error message. *** **Pending** A check run has started and is awaiting its result. *** **Unknown** The status could not be determined, for example, a run did not complete or the check was reset. Unknown results are not treated as failures. *** **No data** No check runs were recorded for that part of the timeline. ## Available checks The following checks are available by default. *** **Live platforms connectivity** Verifies that every enabled live trading platform is reachable. *** **Demo platforms connectivity** Verifies that every enabled demo trading platform is reachable. *** **Visual customization** Verifies that the base resources, such as logos, favicons, and backgrounds, and a color scheme are configured on the [Visual customization](/back-office-guide/system/visual-customization.md) page. *** **New Registration settings** Verifies that client registration is enabled and that at least one registration configuration is enabled on the **System** > **Registration** page. --- # 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.b2core.b2broker.com/back-office-guide/system/status-checks.md?ask=&goal= ``` `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.