Why did my closed test's 14 days restart?

Check continuous opt-in

For personal accounts created after November 13, 2023, Google requires 12 testers opted in continuously for the 14 days before applying. A tester who opts out and rejoins needs a new consecutive period. A replacement needs their own qualifying period. Google's testing requirement and FAQ.

Ask affected testers when they joined and whether they left. Keep a private note of their replies. Do not turn an invitation date into an opt-in date, or guess a missing date.

Also check the track. An internal tester must leave the internal test before joining the closed test. Google's track eligibility rules.

A review delay is a separate problem

Google says a new submission during review can move an app back in the review queue. Items under Changes not yet sent for review need Send for review. Neither message tells you a tester's opt-in history. Google's publishing workflow.

An update alone is not evidence of a reset: Google's testing FAQ recommends shipping fixes during closed testing. Google's advice on updates.

Compare the date of the warning with your release notes and tester replies. Avoid asking everyone to opt out and back in as a troubleshooting step.

Make a recovery plan

• Record the exact warning, track name, build version and time you saw it.
• Separate confirmed opt-outs, late arrivals and dates you have not verified.
• Ask remaining testers to stay enrolled and send useful feedback.
• Leave time for late arrivals. Treat your own calendar as an estimate; check eligibility in Play Console.
• If the message still conflicts with your records, use Play Console's Help page. Include the message and dates, without publishing tester addresses.

If the message asks for more testing after an application, read what to do when production access is refused.