If exports to Google Sheets or BigQuery fail with a reconnect error, or your Google integration shows Needs Reconnect, Google has stopped accepting the saved sign-in for that account. This is usually not a Sheets or BigQuery setup problem in SyncRange.
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.
See Connecting Your Google Account if you need step-by-step connection instructions.
Workspace admins can enforce session length, reauthentication, or restrictions on third-party apps that access Google Cloud and BigQuery. Those policies can cause SyncRange to need reconnect more often than personal Google accounts.
Ask your Google Workspace admin to review:
Allowing SyncRange as a trusted OAuth application (or relaxing overly strict session policies for users who run automated exports) reduces repeated reconnect prompts without weakening security for the whole organization.
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).
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.