Connector Failures
A connector failure prevents files from syncing from Google Drive or OneDrive into your Hubrix document library. Here is how to diagnose and fix the most common connector problems.

Step 1: Read the error message
When a connector fails, it shows a red Error badge. Click the connector in Settings → Data Connectors to open its detail panel. Look for the error message in the Status section — it is usually specific enough to identify the cause.
Step 2: Token expired — reconnect OAuth
Symptom: Error message contains "token expired", "unauthorized", or "401".
Cause: The OAuth access token Hubrix uses to read your Drive/OneDrive has expired or been revoked.
Fix:
- Click Reconnect on the connector detail panel.
- Complete the OAuth flow with your Google or Microsoft account.
- After reconnecting, click Sync now to verify the connection works.
Tokens expire naturally over time. Some corporate Microsoft 365 environments have shorter token lifetimes. If your connector expires frequently, check with your IT admin about whether there is a policy shortening token validity.
Step 3: Permission removed — re-authorise
Symptom: Error message contains "403", "forbidden", or "insufficient permissions".
Cause: The Google or Microsoft account used for the connector no longer has access to the connected folder, or the Hubrix app permission was revoked from the account's settings.
Fix:
- Check that the Drive/OneDrive folder still exists and that the connected account has read access.
- If the Hubrix app was revoked, click Disconnect then Connect to re-authorise.
- During reconnection, grant all requested scopes.
Step 4: Folder deleted — remove and re-add
Symptom: Error message references a specific folder ID or says "folder not found".
Cause: A folder that Hubrix was configured to sync has been renamed or deleted in Drive/OneDrive.
Fix:
- Click the connector and go to the folder list.
- Find the folder showing the error.
- Click Remove to remove it from the sync configuration.
- Click Add folder and select the correct (existing) folder as a replacement.
Step 5: Other error codes
| Error type | Likely cause | Fix |
|---|---|---|
| 429 Too Many Requests | API rate limit hit | Reduce sync frequency or wait; auto-retries after a delay |
| 500 / 503 | Google or Microsoft service outage | Wait and the connector will auto-retry |
| "Conversion failed" | Google Workspace file failed to convert | Re-check the source file is not corrupted; try a manual sync |
After fixing a connector error, always click Sync now to confirm the fix worked before relying on the next scheduled sync to verify it.
Was this helpful?