---
title: "Compare a deploy's Cloud Run revisions during a traffic split | Proofline Help"
description: "The deployment page reads a deploy's Cloud Run revisions apart from the older ones while traffic is split between them."
url: https://proofline.sh/help/deploy-cloud-run-traffic-split/
---

[Help center](/help/)

# Compare a deploy's Cloud Run revisions during a traffic split

The deployment page reads a deploy's Cloud Run revisions apart from the older ones while traffic is split between them. You see how the new revisions behave beside the ones they replace. These comparisons are records only: a check's result, gaps and reports still come from its reading of all serving revisions together.

## Read a split at a deploy check

When a check finds Cloud Run splitting traffic, the signal's reading for that check under **Signals** carries two verdicts. **Merged** gives the check's own verdict, from all revisions together. **Split** compares this deploy's revisions with the others, which stand as the baseline, by the signal's tolerance, as in **Split within tolerance**; it reads **Split unknown** when the sides could not be compared per request, and **Traffic split** when a side was not read. Below the signal's row, a line named for the check, such as **20 min · traffic split**, lists the two sides:

-   **This deploy**: the revisions that serve the deploy's commit, with their combined share of traffic.
-   **Other revisions**: every other revision serving, with their combined share.

Each side shows the signal's reading over the check's window. A signal compared as a share of requests also shows each side's share of requests, and a sum or count shows its value per request. Point to, focus or tap a reading to see the side's revisions with their shares, the window and the query digest. A side that returned no reading reads **Not read**. When the sides could not be compared, a sentence below them says why, such as a service serving more than four revisions or no traffic signal to compare the sides per request.

## Follow a rollout before it lands

A deploy's checks start when it lands, but a staged rollout splits traffic before then. Rollout checks read that split for a GitHub deployment to Cloud Run. They are off by default, and an organization administrator turns them on:

1.  Open the environment's **Setup → Deploy verification** page.
2.  Under **Deploy checks and alarms**, select **Check traffic splits during rollout**. **Check each deploy** must be on too.

From the deployment's first in-progress status, Proofline reads its Cloud Run services about every 12 minutes, until the deployment finishes or two hours pass. Each read that finds the deploy's commit serving beside another commit records a rollout check, and a read that finds no split records nothing.

The deployment page lists them under **Rollout checks**, above **Signals**, oldest first and each named by its window. Each watched signal shows its split verdict beside its name, **Regressed**, **Within tolerance** or **Unknown**, and the two sides as above. A rollout check with no signal to compare lists each revision with its share of traffic and marks the deploy's own. A read that could not complete names the gap instead. Rollout checks decide nothing and send no report, and the deploy's own checks at landing read none of them.

## Related guides

-   [Compare landing and follow-up verification windows](/help/deploy-check-time-windows/)
-   [Identify the commit serving on a Cloud Run revision](/help/deploy-cloud-run-commit/)
-   [Pause deploy verification or alert intake](/help/environment-pause-deploy-checks/)
