Debugging / Connectors
Integration Sync Failures
Connector syncs fail for a small number of reasons — expired authorization, changed permissions, or removed source content.
Causes
The usual causes
- Authorization expired
- The connected account’s access was revoked, the password changed, or the grant expired. Reconnect the integration to restore it.
- Permissions narrowed
- The connection still works but can no longer see a folder, repository, or page. Re-check what was shared with it.
- Source content moved
- Renamed or deleted items cannot be synced. This shows up as failures for specific items rather than the whole sync.
- Provider throttling
- The upstream service limited requests. Syncs back off and continue; a large first import simply takes longer.
- Unsupported content
- Files that cannot be read as text are skipped rather than failing the run.
Recovery
Recovering a sync
- Open the integration in the dashboard and read the status of the most recent run.
- Distinguish “whole run failed” from “some items failed” — the first is usually authorization, the second is usually content.
- Reconnect if authorization is the cause, then trigger a fresh sync.
- Confirm the source item is still present and shared with the connected account.
- If items keep failing after that, note the integration and a failing item reference for support.
A failed sync never deletes memories that were already imported, so re-running a sync is safe.
Was this page helpful?