A Disconnected status means Leanmote's stored credentials for an integration are no longer valid. Sync stops; existing data is preserved.
Common causes
OAuth refresh failure — the long-lived refresh token expired or was revoked.
User left the organization — if the integration was installed under a personal account and that user no longer exists, the provider revokes access.
Admin revoked the app — someone removed Leanmote from the connected tool's authorized applications list.
Password change with mandatory re-auth — some providers force re-authorization after password resets.
How to recover
Open
Administration → Productivity Tools.Find the integration showing Disconnected.
Click Reconnect.
Follow the OAuth flow with a user who has the appropriate permissions. Prefer a service account or org-install path so this doesn't recur on staff changes.
Once reconnected, sync resumes automatically. No data loss occurs — the gap during disconnection is the only missing window.
Prevent it next time
Use org-level installs (e.g., GitHub App on the org, Atlassian site-admin install) rather than personal-account installs.
Set up a notification so an admin is alerted the moment an integration disconnects. See Organization settings.
Document who currently owns each integration in your team's runbook.
Data during the gap
Events that occurred while the integration was disconnected are typically backfilled on reconnection, subject to your plan's history depth. Some webhook-only events that providers don't replay may be permanently missing — pull-based incremental sync usually catches everything else.
Related articles
Sync isn't completing
Missing data after connect
Integrations overview