Fixing connector errors

A connector in the Error state shows the cause on its card. The common ones:

"OAuth token expired / revoked"

The source system invalidated our access — usually a password change, an admin policy, or a revoked grant.

Fix: press Reconnect on the connector card and re-approve. History and settings are kept; syncing resumes where it left off.

"Insufficient permissions"

The connected account lost access to some of the scanned content (a mailbox, channel or folder).

Fix: either restore the account's access in the source system, or edit the connector's scope to drop the content it can no longer reach.

"Rate limited by provider"

The source throttled us. ProcessTwin backs off automatically and retries with jitter — runs marked rate limited complete later by themselves.

Fix: usually nothing. If it recurs daily, lower the sync frequency or narrow the scope.

"Sync failed" (generic)

Open the run's log drawer — every run keeps a step-by-step log. The last lines name the failing stage. Retry once; if it fails the same way twice, the log excerpt is exactly what support needs (Help → Open a ticket attaches it automatically).

Still stuck?

The sync runs article explains statuses in detail, and a ticket from inside the app arrives with the diagnostic context already attached.