Skip to main content

Missing data after connect

When metrics show dashes or zeros after a successful connection.

An integration shows Connected but dashboards aren't filling in. Here's the diagnostic order to follow.


​

Step 1 — Has the initial sync actually finished?


​

Connected and Synced are different. The integration card surfaces both. Wait for the initial backfill to finish before assuming data is missing.


​

Step 2 — Does the backfill reach that far back?


​

There are no plan tiers and no per-plan history depth — how far back the backfill reaches is set by the integration's own API limits, and some providers cap how far a third-party app can read. If a custom range goes back further than the provider allowed, the older portion shows empty.


​

The other case is a gap in the middle rather than at the start: while an organization's subscription is inactive, ingestion stops entirely, and reactivating does not backfill those days.


​

Step 3 — Did you select the right resources?


​

  • For source-control integrations: confirm the relevant repositories are in the selection list.

  • For planning integrations: confirm the relevant projects/teams are selected.

  • For communication integrations: confirm the channels you care about are included.


​

A resource you switched off looks different from one that never synced. Extraction skips repositories and boards that aren't active, but the dashboards don't filter on that flag — so everything already ingested stays on screen. The symptom is a metric that is frozen rather than empty: the numbers are there, they just stopped moving on the day the resource was switched off. If a chart looks plausible but hasn't changed in weeks, check the selection before checking the sync.


​

Step 4 — Are status mappings configured?


​

For Jira and similar tools, cycle time and WIP need active vs. waiting state classification. If statuses aren't mapped, those metrics stay empty even when issue data is present.


​

Open the integration's status mapping inside Administration → Integrations and verify each status is classified.


​

Step 5 — Are users mapped?


​

If GitHub users haven't been mapped to Leanmote teammates, per-team metrics may show empty even though raw activity is captured. See Users management for mapping steps.


​

Step 6 — Is the data source accidentally excluded?


​

Filters on the dashboard or View can hide data. Reset filters to verify whether the issue is filter-side or sync-side.


​

Common confusing patterns


​

  • A metric shows zero only on weekends — your workweek setting may be excluding the days. Check Organization Settings.

  • A metric shows empty only for one team — that team's mapping or status classification likely needs attention, not the integration.


​

Related articles


​

  • Sync isn't completing

  • Why a metric looks off

  • Users management

  • Plan limits and history depth

Did this answer your question?