A rejected Google verification code may belong to an older request, a different account, or a different verification method. Check the challenge before repeatedly requesting replacements.
Identify which code is expected
A text-message code, an Authenticator code, and an eight-digit backup code are separate methods. Enter the type requested by the sign-in screen. A code that is valid for one service or account does not prove ownership of another.
When using Authenticator, inspect the service and account label on the selected entry. Several entries can show similar names, especially after adding another account or replacing a phone.
Match the current request
Google’s 2-Step Verification troubleshooting guide says that if you request multiple verification codes, only the newest one works. Use the most recent message associated with the active challenge rather than a delayed text from an earlier request.
Do not keep several recovery tabs open and move codes between them. Finish one identifiable attempt or follow the current flow’s restart instructions.
Check expiry and input
- Read the latest code carefully and avoid extra characters.
- Enter it before the displayed validity period ends.
- For Authenticator, use a current code and check the phone’s system time if failures continue.
- For backup codes, use an unused code from the current set.
Generating a new backup-code set invalidates the previous set. Waiting for an old backup code to become valid will not help, and changing the device clock does not repair it.
Respect method-specific restrictions
If Google reports too many attempts or temporarily disables that recovery option, follow the displayed retry instructions. Use another previously configured method if offered.
Some sensitive verification flows require a trusted passkey or physical security key and do not accept an SMS code. Read the challenge instead of assuming a six-digit code is always sufficient.
Keep codes out of support messages
Enter codes only in the legitimate flow you initiated. Do not send a screenshot containing a live code to a helper or read it to a caller. If no supported method works, use official recovery from a familiar device rather than disabling protection or deleting the account.
Official references
- Fix common issues with 2-Step Verification
- Get verification codes with Google Authenticator
- Sign in with backup codes
- I'm having trouble resetting my password
Reviewed against Google’s official guidance on October 27, 2026. Available options and screen labels can vary by account, device, region, and organization policy.