Interpret the deploy verification breakdown
Select Breakdown on the environment’s Deploys tab. Check the status of the deploy itself alongside its delivery outcome and signal results.

Read the verification states#
Breakdown counts each deploy in one state. The status at the end of a deploy's row uses a shorter label for the same state.
| Breakdown | Deploy's status | What it means |
|---|---|---|
| Verified at all four checks | No regression | All four checks read the running commit and every signal the deploy compares. |
| Verified until replaced | No regression until replaced | A later deploy replaced this one after its landing check, and every check before then read the running commit and signals. The later deploy's checks cover the time after. |
| Not set up | Not set up | The environment watched no signal when the deploy landed, so its checks ended incomplete. A deploy to ECS whose rollouts finished at every check is verified instead. |
| Incomplete | Checks incomplete | A check could not establish what it reads, or the deploy has a change-check gap. This includes a deploy whose GitHub deployment task is mapped to Cloud Run or ECS services that no watched signal names where they run: the environment watched signals, but the deploy compared none of them. |
| Check not recorded | Check not recorded | A check came due, or verification ended, without a result. |
| Landed without verification | Not verified | The deploy landed, and this environment did not verify it, as when it landed while the environment's checks for new deploys were off. |
| Replaced before it was checked | Replaced | A later deploy replaced this one before it was checked. |
| Checks not yet due | Checking | Verification is running, and its next check has not come due. |
| Deployment failed | Deploy failed | GitHub reported failure or error as the latest status for a job's latest attempt. One failed job makes the whole deploy read Deploy failed, even if that job succeeded earlier. A successful re-run of a failed job replaces its failed attempt. |
| Inactive, never seen landing | Never landed | The deployment was only ever reported inactive. |
A deploy whose checks recorded a regression reads Regressed, whatever its state. Only Deploy failed outranks it, so a deploy never reads better than its checks. A regression does not change a deploy's state: a regressed deploy whose checks read every signal and whose change check is complete counts as verified. Breakdown also lists Regressed, the window's regressed deploys whatever their state, so a regressed deploy is counted there and in its state.