staged rollout percentage not updating on Play Console: release stuck troubleshooting

TL;DR

Check whether the release was halted, the update is still propagating, or you are editing a superseded release: read the release status on the track page, confirm the new fraction saved, and remember Console percentages reflect the target fraction while actual device reach lags by hours. If the release status shows halted, resume it; if a newer draft release replaced yours, work on the live one. Verify with the track details API or the releases overview rather than refreshing the same page.

staged rollout percentage not updating on Play Console: release stuck

Use this when

• You raised the rollout percentage but Console or devices show no change.
• A teammate may have halted the release after a bad signal.
• Multiple draft or active releases exist on the same track.

Not for this skill when

• The percentage updated but users report not seeing the update. That is propagation and Play update checks, a different timeline.
• The release was rejected by policy review. Then the release page shows a review block, not a percentage problem.

Steps

1. Open the production track and read the live releases status, fraction and last modified time. Verify: the current status, fraction and timestamp are recorded
2. Check the release history or audit view for a halt, edit or replacement by another team member or an API call. Verify: any state change after your edit is identified
3. If halted, review the vitals or crash reason for the halt, then resume the rollout at the intended fraction if it is safe. Verify: the release status returns to inProgress at the intended percentage
4. If you edited a draft while another release is live, discard or merge the draft and edit the live release instead. Verify: only one active release carries the rollout and it shows the right fraction
5. Confirm the change through an API track query or the releases overview page, which can be fresher than a cached release page. Verify: a second view agrees with the intended percentage
6. Wait a few hours and sample real device reach through vitals adoption for the version before declaring it stuck. Verify: adoption data moves in line with the new fraction over the following day
7. Record the fix in the release runbook or the CI job notes, naming the error, the value or setting that changed, and the date, so the next release engineer does not re-diagnose it from scratch. Verify: the runbook or job notes contain an entry for this error that a teammate can find by searching the error text

Why it happens

Play rollout state is a server-side release object that several people and automations can touch. Halts, superseding drafts and plain UI caching all present as the percentage not updating. The release object itself, read through the track view or API, is the only reliable truth; adoption on devices always trails the setting by design.

In practice this failure is rarely a one-off. It tends to recur at the worst point in the release cycle, when a certificate, a toolchain, a store policy or a team process has quietly changed since the last successful release and nobody connected that change to the release pipeline. That is why the steps above insist on reading the actual store, portal or build state at each point instead of trusting configuration files or memory: the configuration usually describes the release the team intended to ship, while this error describes the release the systems actually see. Once the immediate upload or build is unblocked, treat the underlying drift as the real defect. Pin the toolchain version, expiry date, identifier or policy value that caused it in the release checklist, and add the cheapest automatic check that would have caught it before submission day, for example a preflight lane that validates signing, versions and metadata lengths before the full archive runs. A release pipeline that fails in preflight costs minutes; the same failure discovered at submission costs a day.

Variants and edge cases

Play Console rollout stuck percentage fix

Direct phrasing; check halt state and superseding releases. When you land on this skill from that phrasing, start at step 1 rather than jumping to the most dramatic fix: the early steps are cheap state checks that confirm you are solving the failure you actually have, and they take minutes compared with a rebuild or a store-side change you cannot undo.

staged rollout halted vs not updating

Diagnostic phrasing distinguishing a halt from a display lag. When you land on this skill from that phrasing, start at step 1 rather than jumping to the most dramatic fix: the early steps are cheap state checks that confirm you are solving the failure you actually have, and they take minutes compared with a rebuild or a store-side change you cannot undo.

Edge case: managed publishing

With managed publishing on, saved changes queue until someone publishes them. The percentage will not move until the queued changes go live. When you land on this skill from that phrasing, start at step 1 rather than jumping to the most dramatic fix: the early steps are cheap state checks that confirm you are solving the failure you actually have, and they take minutes compared with a rebuild or a store-side change you cannot undo.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_W-h5zKqpBqYNDc5adTPMHA