Google Account Needs Reconnect

What is happening

SyncRange keeps a secure connection to your Google account so scheduled exports can run without you signing in each time. Google can invalidate that connection and require you to sign in again. When that happens, SyncRange marks the account as needing reconnect and exports to Google Sheets or BigQuery will fail until you reconnect.

Reconnecting in SyncRange fixes the issue until Google asks again. Some organizations see this regularly because of Google Workspace security policies, not because of a misconfigured export or destination.

How to fix it in SyncRange

1. Open Apps and go to your Google integration dashboard.
2. Click Reconnect Account and complete the Google sign-in flow.
3. Retry the export or wait for the next scheduled run.

See Connecting Your Google Account if you need step-by-step connection instructions.

If you use Google Workspace

Workspace admins can enforce session length and reauthentication for apps that use Google Cloud scopes (including BigQuery). When that interval expires — often every 24 hours — Google invalidates the OAuth connection SyncRange uses for automated exports. There is nothing SyncRange can configure on our side to override that Workspace policy; the fix has to be in Google Admin (or by connecting a different Google account).

You do not need to disable reauthentication for your whole organization. Google supports marking specific apps as Trusted and exempting those trusted apps from the Cloud session reauthentication policy, while keeping the 24-hour requirement for human user logins.

Option 1: Exempt SyncRange as a trusted app (recommended)

Your Workspace admin should do both steps below. Marking the app Trusted alone is not enough — you must also enable the exempt-trusted-apps setting under Google Cloud session control.

Step A — Mark SyncRange as Trusted

1. Sign in to the Google Admin console as an administrator.
2. Go to Security → Access and data control → API controls.
3. Click Manage App Access (or App access control).
4. Find SyncRange in the accessed apps list (or add it by OAuth client ID if it is not listed yet).
5. Change its access level to Trusted.

See Google’s guide: Control which third-party & internal apps access Google Workspace data.

Step B — Exempt trusted apps from Cloud session reauthentication

1. In Admin console, go to Security → Access and data control → Google Cloud session control.
2. Under Reauthentication policy, keep your existing frequency (for example 24 hours) if you prefer.
3. Check Exempt trusted apps so apps marked Trusted are not subject to that interval.
4. Save the setting. Changes can take up to 24 hours.

See Google’s guide: Set session length for Google Cloud services.

After the admin settings apply, reconnect the Google account in SyncRange once (Apps → Google Dashboard → Reconnect Account) so exports pick up a fresh connection.

Option 2: Connect a non-Workspace Google account

If you cannot change Workspace policies, connect a personal Google account (or another account outside that Workspace) to SyncRange instead, then share the destination Google Sheet (or grant BigQuery access) with that account.

1. In SyncRange, connect the alternate Google account (or reconnect using that account).
2. Open the destination Google Sheet and use Share to give that account edit access.
3. For BigQuery destinations, grant that account the needed project/dataset roles, then select it when configuring the exporter.
4. Point the exporter at the shared Sheet (or BigQuery destination) and run a test export.

Personal Google accounts are not subject to Workspace Cloud session reauthentication, so this avoids the recurring reconnect cycle without loosening Workspace security for the organization.

Other Workspace checks

• Third-party app access — policies that block or restrict OAuth apps with Google Cloud, BigQuery, Drive, or Sheets access.
• Context-aware access — rules that require step-up authentication for cloud or API access.

Personal Google accounts

If this is not a Google Workspace account, reconnecting should restore exports. Occasional reconnects can still happen when Google rotates tokens or you change account security settings (password change, revoked app access, and similar events).

If reconnect keeps failing or the error returns very frequently on a personal account, contact us at [email protected] and include the export log message and the Google account type (personal vs Workspace).

Sheets and BigQuery

The same reconnect requirement applies whether your destination is Google Sheets or BigQuery. A BigQuery permission or dataset error is different from this reconnect flow — if the message mentions reconnect or expired Google access, start with reconnecting the Google account rather than changing BigQuery project settings.

• Configuring Google Sheets
• Configuring Google BigQuery
• Viewing export logs