---
title: "Find why a CI deploy check is not established | Proofline Help"
description: "A proofline ci deploy step exits 2 when it cannot establish the requested result. Its last line explains why. Exit 2 is never success."
url: https://proofline.sh/help/ci-deploy-not-established/
---

[Help center](/help/)

# Find why a CI deploy check is not established

A `proofline ci deploy` step exits 2 when it cannot establish the requested result. Its last line explains why. Exit 2 is never success. Your team decides whether the pipeline proceeds.

## Open the deploy from the step's log

Above its last line, the step prints one line for each selected deploy and each check through `--until`. Each line names the deploy's GitHub Environment, task, run and attempts, then the check and its result, the deploy's state, its gap codes and its console page:

```
production deploy run 4127 attempt 1: HOUR_1 INCOMPLETE; state INCOMPLETE; gaps SIGNAL_NO_DATA; <deploy page>
```

Open the page at the end of the line for the affected deploy. Each check lists the gaps it recorded. A gap first seen at 20 minutes leaves the landing result unchanged. When an older server omits a check's gaps, the CLI prints the deploy-wide gaps on that line.

## A check did not record HEALTHY, or names a gap

> A check through CHECKPOINT did not record HEALTHY, or a deploy names a gap. The result is not established.

Read the lines through `--until` for a result other than `HEALTHY` or gaps other than `none`. On the deploy's page, **Checks** lists each result. **Incomplete** means the check could not establish something it reads, such as which commit is running or a signal's value. The page names what it could not read beside the signal or service.

## A later deploy replaced this one

> A later deploy replaced the deploy of NAME at SHA before the CHECKPOINT check, so that check will not be recorded: PAGE. The result is not established.

A **Superseded** check means a later deploy replaced this one. Proofline stops checking the earlier deploy. Follow **Replaced by** on its page to read the time after the replacement. The earlier deploy can read **No regression until replaced** and still exit 2 for the requested check. A longer timeout cannot produce that check.

## The deploy has no checks

> Proofline has no deploy checks of the deploy of NAME at SHA, as when deploy checks were off at its landing: PAGE. The result is not established.

The log shows `state UNVERIFIED`. The deploy page reads **Not verified**. Proofline has no checks for it, as happens when deploy checks were off when it landed. Open the deploy page in the message. Waiting longer cannot establish a result for that deploy.

[Interpret the deploy verification breakdown](/help/deploy-status-breakdown/#read-the-verification-states) defines each state.

## Read the gaps

A gap names what Proofline could not establish about the deploy. It can come from a check, or from the deploy's change check: the review that covered the deployed code. A [change-check gap](/help/deploy-change-check-gap/) can leave the deploy marked **Checks incomplete** even when its recorded checks were `HEALTHY`.

An administrator sees each gap that a setup step closes beside that step while the Inbox lists its setup task. Follow the step the page shows. A member does not see setup steps, so send an administrator the deploy's page and the gap codes from the step's line.

Closing a gap does not change this deploy's result. Proofline never rewrites a recorded check, so the setup step affects the checks of later deploys, and this deploy keeps what it recorded.

For the command's options, see the [CI review check reference](/docs/ci/).

## Related guides

-   [Read a deploy's verification](/help/read-deploy-verification/)
-   [Find why a deployment lacks a change check](/help/deploy-change-check-gap/)
-   [Read Proofline results in CI](/help/read-proofline-results-in-ci/)
