Persistent "Gaia id not found for email" 404 on all gcloud calls — account active, commands still succeed

Google Cloud Cloud Foundations & Onboarding
1

Hoping someone has seen this. Every gcloud command from Cloud Shell returns the error below, yet the command still completes and returns correct data.

Error (appears on essentially every gcloud call):

Regional Access Boundary HTTP request failed after retries: response_data={‘error’: {‘code’: 404, ‘message’: ‘Not found; Gaia id not found for email admin@.com’, ‘status’: ‘NOT_FOUND’}}, retryable_error=False

Example: “gcloud run services list” prints this error line and then lists the services correctly. So access clearly works — it appears to be a secondary identity-resolution lookup that’s failing.

The account is org-admin level. Reproducible across:

  • Cloud Shell session restart
  • Browser cookie clear + fresh terminal
  • Many different commands (run services list, logging read, secrets list, IAM policy reads)

Already ruled out:

  • Wrong active account — “gcloud auth list” and “gcloud config list account” confirm the correct primary email is active.
  • Suspended account — Admin console shows the account active.
  • Alias vs. primary — the email is the account’s primary, not an alias.
  • VPC Service Controls — accesscontextmanager.googleapis.com is not enabled on the project, so there is no perimeter (despite the “Regional Access Boundary” wording in the error).
  • Browser/session state — cleared cookies and restarted; error persists.

Questions:

  1. Has anyone traced “Gaia id not found for email” on an account that is active with a correct primary email?
  2. Is this a known Cloud Identity / Gaia backend indexing issue, and does it self-resolve or require a support case?
  3. Any risk while it’s present, given commands complete successfully — or is it cosmetic?

Thanks in advance.

2

experiencing same here.
Moreover the commands like get-iam-policy are working but first line is giving error next line onwards answers are given. Not sure why its happening.

3

Hello,

This is meant to be sorted in gcloud CLI version 576.0.0. If your install is local running a “gcloud components update” will update it.

If this is in CloudShell it may be next week (by the 21st July 2026) before the VM images are all updated, a downgrade to 573 was recommended in the mean time, running “sudo apt-get install google-cloud-cli=573.0.0-0” should correct it for just that session, with each CloudShell VM being ephemeral.