Skip to main content
Solutions for common issues on the hosted SaaS at lanesync.dev. Self-hosted customers should also check container logs.

​
Dashboard shows no milestones

Dashboard empty after installing the GitHub App.
  1. Click Refresh to trigger sync
  2. Verify the GitHub App is installed on the repository (GitHub → Settings → Applications)
  3. Confirm milestones exist in GitHub with linked issues
  4. Self-hosted: check backend logs for webhook delivery errors

​
Milestone stuck in PLANNING

Stage does not advance after creating milestone and issues.
All milestone issues must have assignees.Open each issue in GitHub → Assign a team member → Refresh dashboard.

​
Milestone stuck in DEVELOPMENT

Development stage shows blocking items after merges.
  1. Close all milestone issues via merged PRs (not manual close without merge)
  2. Ensure required CI checks pass on main — names must match sdlc.yaml development.required_checks
  3. Cut release branch (e.g. release/v1.0.0) unless using trunk-based mode
  4. Check stage details for which checks are marked blocking

​
Milestone stuck in TESTING

Testing stage blocked after release branch created.
  1. Verify CI ran on the release branch
  2. Fix failing checks listed in testing.required_checks
  3. Confirm branch_pattern in sdlc.yaml matches your branch name (release/* vs release/**)

​
Rulesets not created

No branch protection after bootstrap.
  1. GitHub App needs Administration: Read & Write (full tier)
  2. Re-approve permissions on the installation
  3. Re-run repo setup wizard or push sdlc.yaml to trigger ensureRulesets()

​
Phantom BLOCKING badges

Checks show blocking but workflow succeeded, or unknown check names appear.
Stale check names in DB cache. Update required_checks in sdlc.yaml to match current GitHub Actions job names and push to default branch. Webhook re-syncs rulesets and milestones.

​
Production deploy blocked

Deploy workflow refuses to promote.
  1. Evidence PR must be approved (evidencing.required_reviewers)
  2. Deploy gate must return can_deploy: true (requires CI auth — OIDC token or LANESYNC_API_KEY):
  3. Milestone must be in DEPLOYMENT stage with all prior gates passed

​
SDLC Enforce always failing

See SDLC Enforce action for action-specific failures.

​
Still stuck?

FAQ

Common questions about SaaS vs self-hosted.

Contact support

Reach the LaneSync team.