Operate a Google connection

Google app login, Gmail OAuth consent, history synchronization, and Pub/Sub watch are separate connections. Identify the failed stage before changing configuration. See Google Cloud setup for prerequisites.

Symptom	Check
Google login absent	Enabled connector and complete app-login credentials
Login works, Gmail unreadable	Mailbox consent, active connection, and import state
API returns SERVICE_DISABLED	API enabled in the mailbox OAuth client's own Cloud project
No new mail	History worker first, then watch and authenticated Pub/Sub routing
Content locked	Correct owner's key and unlock state
Write pending	Original operation and provider confirmation in Sync Center

For revoked consent, reconnect through the application. Do not replay expired callbacks or tokens. Back up Google credentials and grant-encryption keys separately. The environment archive does not necessarily include mounted credential files.

Preserve keys, local data, and object storage. A full reset is not normal connection repair. Apply any scoped runtime change through the supported runtime guide.