> 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

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" %} <i class="fa-triangle-exclamation">:triangle-exclamation:</i> **1 · Scan Issue**\
The build scan reported errors.
{% endhint %}

{% hint style="warning" %} <i class="fa-circle-exclamation">:circle-exclamation:</i> **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" %} <i class="fa-circle-xmark">:circle-xmark:</i> **3 · Failed**\
At least one quality gate does not meet its criteria.
{% endhint %}

{% hint style="success" %} <i class="fa-circle-check">:circle-check:</i> **4 · Passed**\
All quality gates meet their criteria.
{% endhint %}

Statuses apply to each reported application build. They can differ across build history.

<figure><img src="/files/tWAapkLb1RneKtHuvwZX" alt="SeaLights Dashboard build history with build-status indicators."><figcaption><p>Build status can differ across the application’s build history.</p></figcaption></figure>


---

# 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.sealights.io/knowledgebase/setup-and-configuration/monitoring/sealights-cockpit/dashboards-build-statuses.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.