gcloud: ERROR: (gcloud.auth.print-access-token) There was a problem refreshing your current auth tokens: Reauthentication failed. cannot prompt during non-interactive execution
Your cached Google credentials expired or require a fresh login (session control or password change), and gcloud can't prompt.
Reauthentication failed. cannot prompt during non-interactive executionThere was a problem refreshing your current auth tokensinvalid_grant: Bad Request gcloudReauthentication required. Please run: gcloud auth logingoogle.auth.exceptions.RefreshError: ('invalid_grant: Token has been expired or revoked.' Meaning
Run gcloud auth login (and gcloud auth application-default login for ADC). Organisations set session length (e.g. 16 hours) so tokens must be refreshed. In CI use a service account or Workload Identity Federation, not user credentials.
Common causes
- Org session-length policy expired the login
- Password/2SV change revoked tokens
- Non-interactive CI using a user account
- Refresh token revoked or unused for long
- Multiple accounts with the wrong one active
⚡ Quick fix
gcloud auth loginandgcloud auth application-default login- In CI use
google-github-actions/author a service account gcloud auth listandgcloud config set account ...
Detailed fix by platform
gcloud
gcloud auth revoke --all && gcloud auth login
How to diagnose
- Context — Interactive or CI?
- Policy — Session length?
- Account — Right one?
🔧 Still not fixed?
Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:
Similar errors
- API has not been used in project before or it is disabled Google Cloud: 403 SERVICE_DISABLED — Cloud Resource Manager API has not been used in project 123456 before or it is disabled. Enable it by visiting
- Artifact Registry: Permission artifactregistry.repositories.uploadArtifacts denied Docker push: denied: Permission "artifactregistry.repositories.uploadArtifacts" denied on resource "projects/p/locations/l/repositories/r"
- BigQuery: Access Denied: Project: User does not have bigquery.jobs.create permission BigQuery: Access Denied: Project my-project: User does not have bigquery.jobs.create permission in project my-project
Most viewed in Google Cloud / Firebase
- Missing or insufficient permissions Firestore: FirebaseError: [code=permission-denied]: Missing or insufficient permissions
- Container failed to start Cloud Run: The user-provided container failed to start and listen on the port defined provided by the PORT=8080 environment variable
- 409: The resource already exists Compute Engine: ERROR: (gcloud.compute.instances.create) Could not fetch resource: The resource 'projects/p/zones/z/instances/vm-1' already exists
Other ways to find it
Where this error sits
Origin: Platform & cloud. Errors that are often confused with or caused by this one (click to open):
🧠 Still stuck? Analyze your error
Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.
💬 What worked for others
No tips yet — did something else fix this for you?
Share what worked for you
Tips are checked by an editor before they appear. Links are removed.
Report a correction or suggest an improvement
Last updated 4 Nov 2026