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 → Integrations.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 — a GitHub App on the organization, an Atlassian site-admin install — rather than personal-account installs. This is the single change that prevents most recurrences.
Document who currently owns each integration in your team's runbook.
There is no alert for this. Leanmote does not notify anyone when an integration disconnects, and the Notifications section in settings is about dashboard notifications, not integrations. Until that exists, the only reliable detection is somebody opening the integrations page — which is why the runbook line above matters more than it looks.
Data during the gap
On reconnection Leanmote re-reads history rather than resuming from the disconnect, so a short gap usually fills in. Two limits decide how much comes back, and neither depends on your plan — there are no plan tiers and no per-plan history depth in Leanmote:
The extraction window. Jobs are dispatched with a bounded look-back, one year by default.
What the provider will still serve. Some APIs cap how far a third-party app can read, and events a provider never replays — certain webhook-only signals — stay missing whatever Leanmote does.
Related articles
Sync isn't completing
Missing data after connect
Integrations overview