Skip to main content

Sync isn't completing

Diagnose stuck or stalled integration syncs.

If an integration's status shows Syncing for longer than expected, work through this checklist before contacting support.


​

Expected sync timing


​

The first sync is the slow one, because it reads history:


​

  • Small workspaces: minutes.

  • Medium workspaces: 30 minutes to a few hours.

  • Large workspaces with deep historical backfill: up to 24 hours.


​

After that, refresh runs on a schedule rather than continuously — roughly every twelve hours. A separate sweep runs every fifteen minutes to close out extractions that have finished.


​

This is the single most useful thing to know before diagnosing anything: a "last synced at" timestamp several hours old is the normal state, not a symptom.


​

Step 1 — Check the integration card


​

  1. Open Administration → Integrations.

  2. Find the integration. Note the status (Syncing, Connected, Disconnected) and the "last synced at" timestamp.

  3. Give it more than a full cycle before calling it stuck. A timestamp that hasn't moved in an hour, or in eleven, means nothing. Past roughly a day with no movement on an active integration, something is wrong.


​

Step 2 — Look for credential issues


​

  • OAuth tokens occasionally expire silently. Disconnect and reconnect the integration to refresh the token.

  • If the connecting user has left your org, the install may have been revoked on the provider side. Reinstall using a service account or the org-level install path.


​

Step 3 — Check provider rate limits


​

Hit a provider rate limit and Leanmote backs off automatically; sync resumes once the window resets. The budgets differ per provider and change over time — GitHub, GitLab and Atlassian each publish their own, and some are cost-based rather than a flat request count, so check the provider's current documentation rather than a number quoted here.


​

If you're consistently rate-limited, narrow the integration to fewer repositories or projects.


​

Step 4 — Check provider status pages


​

If GitHub, Atlassian, Slack, etc. are having an outage, sync stalls. Check the provider's status page before assuming Leanmote is the problem.


​

Step 5 — Reconnect


​

If none of the above explains the issue, disconnect and reconnect the integration. The next initial sync resumes from the last good state.


​

Still stuck?


​

Reach our support team via the Intercom Messenger in the bottom-right of the app. Include the integration name, the last good sync timestamp, and any error messages visible on the integration card.


​

Related articles


​

  • Integration shows disconnected

  • Missing data after connect

  • Integrations overview

Did this answer your question?