Troubleshooting

Symptom-first playbooks to fix common setup, sync, and login issues on your own. Each section lists numbered steps in the product UI — no operator access required.

Still stuck after these steps? Use the in-app feedback form, email support with your organization login and the section you followed, or ask in the DeliveryCompass Discord (discord.gg/QhHyfNaGqr).

1. This usually means bootstrap succeeded at org level but repositories are not mapped to teams yet.
2. Open Teams & repos and drag repos from Unassigned onto team cards.
3. Return to Overview or Team analytics and refresh.

See Teams & repos guide.

Onboarding can finish before the worker marks baseline import complete. Symptoms: empty charts, zero throughput, or a setup banner still visible.

1. Wait 5–15 minutes and refresh the dashboard — large orgs may take longer.
2. Confirm your PAT is valid in GitHub setup (invalid token steps).
3. If nothing changes after several hours, contact support with your org login. Operators can check import status in backoffice.

1. Open Start setup or the onboarding banner and confirm every step shows complete.
2. If you just finished, wait a few minutes — large organizations can take longer to import pull requests. Refresh the dashboard.
3. Open Teams & repos and drag repositories from the unassigned pool onto team cards. Team KPIs stay empty until repos are mapped.
4. Check GitHub setup in the user menu — your token must validate with read:org and repo scopes.

1. Go to Teams & repos.
2. Drag each active repository from the unassigned pool onto the team that owns it.
3. Return to the dashboard and select the team — metrics only include mapped repos.

See the Teams & repos guide for mapping rules.

1. In GitHub, create a new personal access token with read:org and repo (read-only is fine).
2. In DeliveryCompass, open GitHub setup from the user menu (top right).
3. Paste the new token and save. Wait for validation, then refresh the dashboard.

Your GitHub token is only used for data import — it is not your DeliveryCompass login password.

1. After setup, the first import runs in the background. This is normal for organizations with many repositories or years of pull request history.
2. Refresh the dashboard every few minutes — org-level stats may appear before all team KPIs.
3. If it has been more than a few hours with no change, check your token in GitHub setup and follow invalid token steps.

1. DeliveryCompass syncs GitHub data on a daily cadence — yesterday’s merges may not appear until the next run. See sync schedule.
2. On the dashboard, use Refresh after a sync completes to reload computed KPIs.
3. Confirm your GitHub token is still valid in GitHub setup.

1. Confirm the event falls inside the chart’s time range — markers respect the toolbar range.
2. For GitHub releases and tags, wait for daily sync and check Chart milestones lists synced events for that range.
3. Verify your GitHub token is valid and repositories are mapped (not excluded or forks).
4. On the chart, check the milestone legend below the series legend — a hidden type removes its markers.
5. See the Chart milestones guide and FAQ.

1. Check the time range on the dashboard toolbar — compare the same window across teams.
2. Verify repos are mapped on Teams & repos — unassigned repos do not count toward team KPIs.
3. Read the confidence column on team cards — low confidence means fewer merged PRs in the window.
4. See the metrics glossary for how each KPI is calculated.

1. Use the email and password you created during setup — not your GitHub token.
2. On Forgot password, enter your work email and follow the reset link.
3. Check spam for the reset email. If nothing arrives, contact support — SMTP may be disabled in your environment.

1. Check spam and promotions folders.
2. Open Profile and confirm Weekly digest is enabled.
3. Weekly emails send after the Sunday sync — see weekly summary guide.

If another account registered your GitHub organization login first, you cannot access their data from a second signup. Each pilot workspace is tied to one registrant.

Options: use the account that originally registered the org, or see accounts & access for pilot limitations.

1. Team names are imported from GitHub — create teams in your GitHub organization if none exist yet.
2. After creating teams, reconnect your token in GitHub setup or wait for the next daily sync.
3. You can still see organization-level metrics while team cards populate.