When a work verification code is missing, the problem is often routing: alias, filter, forwarding destination, category, or a different account address. Check in this order: which address the vendor thinks you are, what your own Gmail rules did with the message, and only then what the Workspace admin's routing did before the mail ever reached you.

Quick answer

Pull up the vendor's account profile and read the address on file, character by character, against the aliases you actually hold. Search the work Gmail everywhere, Spam and All Mail included, before requesting another code. Once the mailbox is provably empty, the trail points upstream to admin routing, and that conversation belongs with IT.

Situation	What it usually means	Better next move
Alias	The service profile uses an alias.	Search the alias, not only your primary mailbox.
Forwarding	Mail routes to another inbox.	Check the forwarding destination and original inbox.
Filter	A rule skips Inbox or applies labels.	Review Gmail filters and blocked addresses.
Category	The message is in Updates or Promotions.	Search categories with provider words.
Admin path	The work account is managed.	Use IT/admin recovery instead of guessing.

Confirm the account address before searching

HR renames, marriage renames, and team address migrations all leave vendors mailing an address nobody watches anymore. Ask the vendor page to display the destination it has on file, then compare it with the send-as addresses and aliases listed in your Gmail settings. Ten seconds of comparison regularly explains an hour of fruitless searching, because a code delivered to jsmith@ will never surface in searches scoped to john.smith@. Search by delivery address instead: deliveredto:jsmith@company.com newer_than:1d. If several work tools fail this way, see logging into five tools every Monday.

Inspect Gmail routing deliberately

Open the filter list in Gmail settings and read every rule that mentions the vendor's domain, the word verification, or some vendor-noise label. Role accounts inherit filter sets from predecessors, and one skip-inbox rule written by an owner two handovers ago can eat security mail indefinitely. Edit the suspect rule, trigger one fresh code, and check where it lands. The Gmail filter guide shows how to read each rule, and the forwarding guide covers rules that send mail elsewhere.

Use the workplace recovery path

When the mailbox checks come up clean, the block sits upstream in Workspace routing, quarantine, or a compliance gateway, none of which is visible from your seat. File the IT ticket with what you can prove: the vendor's send timestamp, the exact destination address, and the searches that returned nothing. That evidence lets the admin trace the message in delivery logs instead of asking you to try again tomorrow.

Where MagicLess fits

MagicLess helps with the half of this problem that lives inside your own mailbox: once the vendor's code reaches any folder of the connected work Gmail, it gets surfaced at the login page without a manual expedition through Spam and All Mail. It cannot see into admin quarantine, will not make a blocked message deliver, and never fills the vendor's form on its own.

Claim ledger

Claim	Source	Last checked
Gmail lets one mailbox send and receive under additional aliases, so a code's destination address can differ from the primary address.	Source	2026-09-13
Gmail filters can alter routing for matching incoming mail.	Source	2026-09-07
Authentication secrets should not be disclosed casually.	Source	2026-09-07
Workspace admins can apply routing and delivery rules that act on mail before it reaches an inbox, on top of a user's own Gmail filters.	Google Workspace Admin routing and Gmail filter rules	2026-09-13

Sources

Google Workspace Admin Help - Email routing and delivery options: https://support.google.com/a/answer/2685650?hl=en
Google Gmail Help - Create rules to filter your emails: https://support.google.com/mail/answer/6579?hl=en
Google Gmail Help - Send emails from a different address or alias: https://support.google.com/mail/answer/22370?hl=en
NIST SP 800-63B - Digital Identity Guidelines: Authentication: https://pages.nist.gov/800-63-4/sp800-63b.html