> 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/build-monitor.md).

# Build Monitor

Use Build Monitor to inspect a reported build and its test stages.

### Open a build

Select an app, branch, and build to open its overview.

<figure><img src="/files/aPLFpPoMrDwlWjggQGKm" alt="Build Monitor build overview showing app, branch, and build selectors."><figcaption><p>Build Monitor opens after you select an app, branch, and build.</p></figcaption></figure>

### Review build session and scan details <a href="#build-session-and-build-scan-details" id="build-session-and-build-scan-details"></a>

The build overview shows the first two commands required to report a build to SeaLights:

* `config` — generates the Build Session ID (BSID).
* Build scan — analyzes the application bytecode.

### Review test-stage details <a href="#test-stage-details" id="test-stage-details"></a>

View Test Stage-specific data by selecting a Test Stage on the right-hand side of the screen.

<figure><img src="/files/MNFQbzdCvbCDJDtuQCDp" alt="Build Monitor showing a selected test stage."><figcaption><p>Select a test stage to view its execution data.</p></figcaption></figure>

#### Review executions <a href="#the-executions-tab" id="the-executions-tab"></a>

This tab lists every execution associated with the selected test stage. These executions contribute to the duration, coverage, and test counters.

{% hint style="warning" %}
When you run the same tests against the same build, the test counters and duration will be aggregated.\
For example, two executions of 10 tests each show 20 reported tests and two executions.
{% endhint %}

Each execution shows its status, start and end times, Lab ID, and ending cause.

<figure><img src="/files/xnur4jHKeyu5aH0wjz9D" alt="Executions tab with execution status, timestamps, Lab ID, and ending cause."><figcaption><p>The Executions tab lists the activity that contributes to test-stage metrics.</p></figcaption></figure>

A test-stage execution has three statuses:

{% hint style="info" %} <i class="fa-play">:play:</i> **Created**\
The execution is in progress.
{% endhint %}

{% hint style="warning" %} <i class="fa-spinner">:spinner:</i> **Pending Delete**\
SeaLights received the end event and is processing it. This state lasts no longer than 120 seconds.
{% endhint %}

{% hint style="success" %} <i class="fa-circle-check">:circle-check:</i> **Ended**\
Processing is complete. Metrics are available in the SeaLights dashboard and reports.
{% endhint %}

<details>

<summary>View ending-cause definitions</summary>

The **Ending cause** column can contain these values:

#### Ended by an agent or API

* **Agent** — an agent command ended the execution.
* **API** — an API request ended the execution.

#### Ended automatically

* **Server - Conflict** — SeaLights detected conflicting execution parameters and closed the older execution. For example, the same Lab ID was used for another test stage.
* **Server - Timeout** — an API-configured timeout ended the execution. The default timeout is four hours.
* **Server - Daily** — SeaLights closes executions that remain open for over 24 hours. This happens daily at 3:00 AM GMT.

#### Ended by Support

* **SeaLights Support** — Support manually ended the execution for troubleshooting or ticket resolution.

</details>

### Troubleshoot advanced cases <a href="#advanced" id="advanced"></a>

#### Review agent command JSON <a href="#json-details-of-agents-command" id="json-details-of-agents-command"></a>

In the Build Scanner and Test Listener tabs, view JSON session parameters mapped from agent commands.

<figure><img src="/files/2Rrh9vc1YsDrw7uEyH4x" alt="Build Monitor panel showing JSON command details."><figcaption><p>Inspect the JSON parameters submitted by the agent command.</p></figcaption></figure>

<figure><img src="/files/b3DmA2wT9q0dSFiqCI6L" alt="Build Monitor showing agent command JSON details."><figcaption><p>Use command details to compare the reported session parameters.</p></figcaption></figure>

#### Validate pull request integration <a href="#validating-pull-request-integration-using-the-build-monitor" id="validating-pull-request-integration-using-the-build-monitor"></a>

Pull request jobs do not appear on the dashboard. Review them in Build Monitor instead.

1. Select the pull request branch. Pull request branches are hidden by default.
2. Select the expected build.
3. Confirm the build session and pull request data.

If the branch or build is missing, review the [Pull Request integration setup](/knowledgebase/setup-and-configuration/integrations/pull-request-integration/configure-pull-request-flow-for-sealights.md).

<figure><img src="/files/3baoj2NgdQpWZBaVzZgt" alt="Build Monitor displaying a pull request branch."><figcaption><p>Enable pull request branches to find pull request build data.</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/build-monitor.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.