You can pause a closed testing track in Google Play Console, and that is usually what people mean by deleting one. But if you are mid-test, do neither. The production access requirement counts 12 testers opted in continuously for the last 14 days, and a paused track stops the test. Pause on day 9 and you are not resuming at day 9 later; the continuous window is broken and the clock starts over when you reactivate. Here is what each option actually does, and what to do instead in the situations that usually trigger the question.
What pausing a track actually does
Pausing deactivates the track’s release. New testers can no longer download the app, and the test is no longer running. Your tester list, the track itself, and existing installs on testers’ phones all survive; what dies is the continuity your production access application depends on. Google’s requirement is a closed test running for the last 14 days, not a total of 14 days collected in pieces.
Can you actually delete a track?
Not in the way people expect. The closed testing track itself stays in your Play Console; what you can do is pause it (deactivate the release) and remove testers from it. For almost every real situation, that distinction does not matter, because the answer to “should I remove this mid-test?” is no.
The situations that make people want to delete the track
- Uploaded the wrong build: do not touch the track. Upload the correct build as a new release on the same track. Testers get it as a normal update, and updating does not reset the 14 days.
- Testers went quiet: replace the testers, not the track. Dropping below 12 does not reset the clock by itself, but weak engagement is what production review rejects, so top the list back up quickly.
- Want to start the test over cleanly: you do not need to. Add or replace testers on the running track. A restart throws away every continuous day you have banked.
- Finished testing and got production access: this is the one time pausing is harmless. Once your app is in production, the closed track has done its job. Many developers simply leave it running for pre-release builds, which is what it is for.
Removing testers vs pausing the track
Removing an email from your tester list removes that person’s access, and your opted-in count drops when they are counted next. That is a normal part of managing a test and completely safe in small numbers, as long as you stay at or above 12. Pausing the track stops the test for everyone. One is a substitution; the other is a forfeit.
Frequently asked questions
Does pausing a closed testing track reset the 14 days?
Treat it as yes. The requirement is a test running continuously for the last 14 days, so a pause breaks the window. When you reactivate, plan on 14 fresh days before applying for production access.
Can I run two closed testing tracks at once?
Yes, Play Console allows multiple closed tracks. Testers on the track with the highest version code get that version. For meeting the 12-tester requirement, one track is simpler and is what we recommend.
Do testers lose the app when I pause the track?
Installed copies stay on their phones, but the app is no longer available to them through Google Play, and the test is no longer considered running.
I paused by accident. What now?
Reactivate the release immediately and keep your testers opted in. Then give it the full 14 continuous days before applying. If some testers dropped away in the gap, Testers Community can refill the list within 6 hours.
