Google OAuth token revoked: restore authorization and review queued work

Define the decision

A connection that worked previously can lose authorization. Treat a confirmed token rejection separately from DNS, TLS or mailbox quota errors. Repeated background failures will not repair a revoked grant.

Work through the procedure

1. Pause affected campaign work while collecting the sanitized OAuth error.
2. Check whether access was intentionally revoked or policy changed.
3. Reauthorize the same mailbox through the supported Google flow.
4. Verify sending and a controlled reply, then review queued steps and uncertain attempts before resuming.

Worked example

The following is a synthetic example for this procedure, not a customer result or performance benchmark.

Last successful sync: before an app-access revocation
Current error: authorization grant rejected
Repair: approved reconnection of the same mailbox
Restart review: pending follow-ups and any uncertain send outcomes

Read the result

Reconnection restores a credential path; it does not prove all missed replies were processed or that queued content is still appropriate. Inspect the affected time window in the inbox.

Check before moving on

1. Confirm the account address after reauthorization.
2. Keep tokens and codes out of logs shared with support.

Limits and next action

If revocation was part of a security response, follow that response before reconnecting. Do not silently restore access against the account owner’s decision.

Source: Google: OAuth 2.0 authorization and token lifecycle