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.

The Production Deploys tab: 1 deploy regressed, and 2 of 3 deploys in the last 7 days were verified. Scale the API service to twelve tasks reads Checking, Retry payment captures once reads No regression and Read checkout inventory in one query reads Regressed. Each row ends with Open.
The regressed deploy counts as verified because its checks read every signal; the newest is still being checked. Fictional demo workspace.

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.

BreakdownDeploy's statusWhat it means
Verified at all four checksNo regressionAll four checks read the running commit and every signal the deploy compares.
Verified until replacedNo regression until replacedA 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 upNot set upThe 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.
IncompleteChecks incompleteA 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 recordedCheck not recordedA check came due, or verification ended, without a result.
Landed without verificationNot verifiedThe 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 checkedReplacedA later deploy replaced this one before it was checked.
Checks not yet dueCheckingVerification is running, and its next check has not come due.
Deployment failedDeploy failedGitHub 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 landingNever landedThe 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.

Search help

Tab to a result. Enter to open. Escape to close.