If an integration's status shows Syncing for longer than expected, work through this checklist before contacting support.
Expected sync timing
Small workspaces: minutes.
Medium workspaces: 30 minutes to a few hours.
Large workspaces with deep historical backfill: up to 24 hours for the initial sync.
Incremental syncs after the initial backfill should complete in seconds to minutes.
Step 1 — Check the integration card
Open
Administration → Productivity Tools.Find the integration. Note the status (Syncing, Connected, Disconnected) and the "last synced at" timestamp.
If the timestamp hasn't moved in over an hour for an active integration, treat it as stuck.
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 after the limit window resets.
GitHub: 5000/hour per token.
GitLab: 1000/hour.
Jira: 1000/hour.
If you're consistently rate-limited, narrow the integration to fewer repos 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