A Gmail filter can make a login code disappear from Primary without stopping delivery. Search the mailbox first, then inspect the rule that moved it.

Quick answer

Keep the sign-in page in front of you and treat the mailbox as evidence. Verify the receiving address, run an everything-included search for the newest official code email, and open the filter list only once the search proves a rule moved the message. Where several look-alike code emails exist, the one to use is the most recent generated by your open attempt; a rejection of that message means recovery time, not more digging.

Situation	What it usually means	Better next move
Archive rule	Message is in All Mail but not Inbox.	Edit or narrow the filter.
Label rule	Message appears under a custom label.	Add a visible login/security label if helpful.
Delete rule	Message lands in Trash.	Remove the dangerous match.
Forward rule	Message goes to another inbox.	Confirm forwarding is intentional.
Broad match	Rule catches too many service emails.	Tighten sender or subject criteria.

Search in All Mail before changing settings

Prove the message exists before you touch a single rule. An in:anywhere search that turns up the code email sitting in All Mail or under a label tells you delivery worked and a rule moved it; a search that finds nothing points away from filters entirely, toward the wrong address or a provider-side delay. Editing rules before you know which case you are in only makes tomorrow's audit harder. The Gmail search guide has more queries.

Audit filters by action

Work down the filter list reading the action column, not the descriptions. Flag every rule that skips the inbox, deletes, or forwards, then ask whether its match terms could sweep up automated sign-in mail: filters keyed on words like "account" or "noreply", or on an entire vendor domain, catch code emails as a side effect. The rule hiding your code is usually one of these accidental broad matches, not something aimed at login mail on purpose.

A code countdown is a bad moment for settings surgery, so sign in first. Then reopen the guilty filter and narrow it: exclude the provider's verification sender from the match, or remove the Skip-Inbox or Delete action, instead of erasing the whole rule and flooding your inbox with everything it used to manage. Trigger one test login afterward to confirm the code email now lands where you can see it.

Where MagicLess fits

The chore that repeats in this scenario is a double hunt: first for the code email a rule tucked away, then for the rule itself. MagicLess takes over the first half on connected Gmail accounts. When a login page wants an OTP or magic link, a single click shows the newest matching message even if it never appeared in your inbox view. It will not edit or disable your filters, cannot conjure mail the provider never sent, and does not vouch for a message that looks off.

Claim ledger

Claim	Source	Last checked
Gmail filters can archive, delete, star, label, or forward messages.	Source	2026-09-07
Gmail supports in:anywhere and label searches.	Source	2026-09-07
Gmail's spam reporting moves messages out of the inbox view, and misclassified mail can be unmarked.	Source	2026-09-13
Repeated retries can create confusing authentication attempts controlled by the provider.	Source	2026-09-07
Gmail search operators and filters are useful for finding or routing login email, but provider authentication rules still decide whether an artifact works.	Google Gmail search operators and NIST SP 800-63B	2026-09-07

Sources

Google Gmail Help - Create rules to filter your emails: https://support.google.com/mail/answer/6579?hl=en
Google Gmail Help - Refine searches in Gmail: https://support.google.com/mail/answer/7190?hl=en
Google Gmail Help - Report spam in Gmail: https://support.google.com/mail/answer/1366858?hl=en
NIST SP 800-63B - Digital Identity Guidelines: Authentication: https://pages.nist.gov/800-63-4/sp800-63b.html