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

​
Installed an App but cannot see the organization workspace

If the account chooser shows only your personal workspace, confirm that you completed GitHub sign-in with an account that can access the same LaneSync App installation. For a new organization workspace with no LaneSync admin yet, use an active owner of that GitHub organization and finish LaneSync sign-in from the App installation page. You do not need to uninstall the App. If the workspace already has an admin, ask that admin for an invite; GitHub organization membership alone does not add you to LaneSync.

​
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

​
Repository setup and release readiness disagree

Open Repositories and the release’s Readiness tab. An active release with incomplete or unverified setup needs setup attention before it can be ready to deploy.
  • Review setup PR / Setup pending: continue the repository wizard. Merging a PR alone does not confirm active protection.
  • Configuration missing: inspect sdlc.yaml and any configured inherited configuration, then complete setup.
  • Branch protection disabled / missing: inspect the rulesets and use the explicit setup action. Refreshing does not reactivate a deliberately disabled rule.
  • Verification unavailable / Setup unverified: check App access and retry. A permission error, rate limit or outage does not mean configuration was deleted.
Status reads and background reconciliation can recover a missed webhook. If a newly accessible repository is missing, verify installation access in GitHub and choose Discover repositories in LaneSync.

​
New repository is missing

  1. Select the LaneSync workspace for the GitHub account that owns the repository. Discover repositories searches only the selected workspace’s linked installation.
  2. On GitHub, configure the LaneSync or LaneSync Lite installation for that account. If access is limited to selected repositories, add the new repository and save.
  3. Return to the dashboard and click Discover repositories, then open Manage repositories & setup. A repository can be discovered before it has any releases or milestones.
  4. Complete the repo setup wizard for the newly discovered repository.
Full and Lite installations both support discovery. You do not need to change tiers to discover a repository that the installed App already has access to. See Adding repositories later.
Sign in again if your session expired or no workspace is selected. Confirm that the selected workspace still has a LaneSync installation and that GitHub grants it repository access. Discovery cannot add repositories for an uninstalled App or one with no accessible repositories.GitHub access failures are reported as discovery errors. Resolve the reported access issue before retrying. A successful discovery response confirms the repository list was refreshed; synchronization continues in the background and can still fail separately.

​
Milestone stuck in PLANNING

Stage does not advance after creating milestone and issues.
All milestone issues must have assignees.Open the release’s Scope & owners tab and assign owners in LaneSync. Use Assign to me or remove one owner with Unassign. Verify the configured planning requirements if the stage still does not advance.

​
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.

​
Expected git tag is missing

CI is green on main or release/v1.0.0, but dev-* or *-rc-* tags never appear.
  1. Confirm the workflow file is a LaneSync template (ci.yml or ci-*.yml). Custom CI is not auto-tagged
  2. The run must be a push that succeeded. Pull requests and failed builds do not create tags
  3. Re-run the successful workflow (or push again) after LaneSync is updated — already-finished runs are not tagged retroactively
  4. Confirm the GitHub App is still installed on the repository
  5. Do not add SDLC_APP_ID / SDLC_APP_PRIVATE_KEY. LaneSync never provisions those secrets; tags are created with the App installation

​
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.

​
Workflow update banner or PR issues

Update banner missing, wrong files in update PR, or banner persists after merge.
See Update LaneSync Workflows — Troubleshooting. Common causes: bootstrap not COMPLETE/LEGACY, stale pending PR, or sdlc.yaml check names not matching workflow name: fields on custom CI paths.

​
Still stuck?

FAQ

Common questions about SaaS vs self-hosted.

Contact support

Reach the LaneSync team.