> For the complete documentation index, see [llms.txt](https://docs.sealights.io/knowledgebase/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sealights.io/knowledgebase/setup-and-configuration/monitoring/sealights-cockpit/dashboards-build-statuses.md).
# Dashboard build statuses
Understand the build statuses shown on the SeaLights Dashboard.
The SeaLights Dashboard shows one of four statuses for each reported build.
When several conditions apply, SeaLights shows the first matching status in this order: Scan Issue, Missing Data, Failed, then Passed.
Select a status on the Dashboard to view its summary and quality-gate definitions.
{% hint style="danger" %} :triangle-exclamation: **1 · Scan Issue**\
The build scan reported errors.
{% endhint %}
{% hint style="warning" %} :circle-exclamation: **2 · Missing Data**\
A metric required by a quality-gate criterion is missing.
For example, no tests were reported for a failed-test criterion. A coverage criterion also requires a reported test stage.
{% endhint %}
{% hint style="danger" %} :circle-xmark: **3 · Failed**\
At least one quality gate does not meet its criteria.
{% endhint %}
{% hint style="success" %} :circle-check: **4 · Passed**\
All quality gates meet their criteria.
{% endhint %}
Statuses apply to each reported application build. They can differ across build history.
Build status can differ across the application’s build history.
---
# 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://docs.sealights.io/knowledgebase/setup-and-configuration/monitoring/sealights-cockpit/dashboards-build-statuses.md?ask=&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.
