On this page
The problem
You can't create a new release, the Start rollout button is disabled, or an existing release won't move forward — it's stuck in review, draft, or a pending state with no clear next step.
Why it happens
Releases pause on one of three blockers: an error that must be fixed before publishing, an outstanding release on the same track that hasn't been rolled out to 100% or discarded, or unmet Dashboard setup tasks that lock the release controls. Google's documentation states that you cannot create a new release while outstanding releases exist, and that errors (not warnings) block publishing.
The quick fix
Open the Publishing overview page — review the Changes ready to send for review section for errors, complete any outstanding setup tasks on the Dashboard, and roll or discard existing staged releases to 100% before creating a new one.
Step by step
Check the Dashboard for unmet tasks
If Create new release is disabled, the Dashboard shows which mandatory setup steps are still incomplete. Resolve them first — app details, store listing, app content, testing, release.
Open the Publishing overview page
Go to Test and release > Publishing overview. Under Changes ready to send for review, click Show more on the release to see the Errors summary.
Resolve errors before warnings
Errors must be fixed before you can publish. Warnings can still publish, but Google recommends resolving them. Click each error for the field it points to, fix it, and save.
Clear outstanding releases on the track
If the track already has a staged release under 100%, roll it out to 100% or discard it. You can only discard the latest release on a track — older drafts or rejected releases may need to be handled in order.
Submit for review if the release is ready
After errors are cleared and outstanding releases are handled, click Review and roll out, then Start rollout to send the release through Google's review pipeline.
Things to check
- Dashboard for unmet setup tasks
- Publishing overview page for errors vs warnings
- Track Releases tab for outstanding or draft releases
- Account permissions for release management
- Release status shown on the Release details page
If this didn't work
- For a release stuck in review: Google's review usually completes within 3-9 days. Check the Dashboard status and wait — do not resubmit unless asked, as each new submission starts a fresh review cycle.
- If the release is stuck in draft while the same track has a prior staged rollout, resolve or discard the prior release first.
- Confirm you have the Release apps to testing tracks permission — without it, Create new release and rollout controls stay disabled.
Common mistakes
- Trying to create a second release while the first is still staged under 100%
- Confusing errors (must fix) with warnings (can publish) — only errors block rollout
- Resubmitting a stuck-in-review release instead of waiting for Google's review window
When to contact Google
If the Dashboard tasks are all complete, no errors remain, no outstanding releases block you, and the Create new release button is still disabled, contact Play Console support with the exact track, release name, and screenshot of the status.
Sources & references
Official Google documentation- Prepare and roll out a releasesupport.google.com
- Release app updates with staged rolloutssupport.google.com
These links open Google's official Play Console Help pages used to verify this guide. AppsTestLab guidance is independent and not affiliated with Google.
Last reviewed August 23, 2026 · Google Play requirements change — verify in the Play Console.