[BUG] Gmail connector stops returning mail addressed to a Workspace alias after a date; the Gmail app still shows it
Status Open
Reported on v2.1.296
Maintainer reply None cached
Activity 0 comments · opened Oct 11, 2026
Summary
The claude.ai Gmail connector, used from Claude Code, stopped returning messages addressed to a secondary alias of a Google Workspace (university) account after 2026-10-05. The same messages show up in the Gmail mobile app for that account. Mail addressed to the account's primary address is still returned normally.
What I see
search_threadswithin:anywhere to:<alias>returns about 200 threads. The newest is dated 2026-10-05 18:59 UTC.- Nothing addressed to the alias after that date is returned, including a message received on 2026-10-08 that the Gmail app shows.
- Mail addressed to the primary address after 2026-10-05 is returned normally (newest 2026-10-10).
- Messages I sent from the account on 2026-10-08 were also not returned by
in:sentsearches.
Searches tried (all returned {})
in:anywhere to:<alias> newer_than:5din:anywhere deliveredto:<alias> newer_than:5d- The sender's domain and distinctive subject keywords, with
includeTrash: true
Expected
Messages delivered to an alias of the connected account are searchable, as they were before 2026-10-05.
Environment
- Claude Code 2.1.296, Windows 11
- claude.ai Gmail connector
- Google Workspace (university) account with a secondary address alias
Notes
I have not ruled out a routing change on the Workspace side around 2026-10-05. Reporting because the Gmail app shows the message in the same account while the connector does not.