How data syncs
- First import
- Last 90 days
- Nightly repair
- 02:00 UTC
- Where to check
- Admin → Sync runs
DevGlimpse imports your history once, then stays current from GitHub’s events. Overnight and hourly checks repair anything that was missed, so your numbers converge on what GitHub says.
The pieces
- 90-day backfill. When you connect an organization, DevGlimpse walks each repository and imports the last 90 days of pull requests, reviews and commits. It runs one repository at a time and respects GitHub’s rate limits. When the limit is spent, the run pauses and resumes by itself.
- Webhooks. After that, GitHub tells DevGlimpse about new and changed pull requests, reviews and comments as they happen. Each event is checked, then applied.
- Nightly repair. Every night at 02:00 UTC, DevGlimpse looks again at each repository’s recently updated pull requests and at team and organization membership. A merge, review, comment or membership change whose event never arrived is fixed by the next night. This run is labeled Nightly reconcile.
- Hourly redelivery. Every hour, DevGlimpse asks GitHub to resend the App’s failed deliveries from the last 24 hours. Each failed delivery is retried once.
- Rollups. Dashboards read daily rollups, one row per person, team or group for each day. DevGlimpse recomputes the affected days after each batch of changes, after team changes and every night.
How fresh is my data?
For most changes, minutes after they happen on GitHub. The nightly repair covers the rest within a day.
To check:
- Look at the sync status at the bottom of the left navigation. It reads Synced with a relative time such as
3h ago, or Backfill 3/12 repositories, Deferred until a time, or Sync failed. Every role sees it. - Select it for details: the last successful sync, backfill progress with Running, Deferred and Failed counts, and a link to View sync runs.
- Managers and org admins can open Admin → Sync runs. It shows three cards, 90-day backfill, Deferred by rate limit and Last successful reconcile, then a table of every run with its status.
Sync states
| What you see | What it means |
|---|---|
| Not connected | No source is connected yet. |
| Backfill n/m repositories or Syncing… | A run is in progress. |
| Deferred until a time | GitHub’s rate limit is spent. Syncing resumes at that time. |
| Sync failed | The latest run failed. The nightly reconcile retries it. |
| Synced with a time | Every latest run completed. |
History window
The first import covers 90 days. Your plan can include a longer history window. The window your workspace has is shown under Admin → License → Plan features as History window.
What gets stored
During a trial, DevGlimpse stores activity only for the contributors you track. Bots and excluded contributors are left out of the metrics. If you choose All repositories (excluding forks), forks are skipped in sync and in the dashboards. See People and identities.