Troubleshooting
Resolve connection, scan, finding, fix and notification problems with the right next step instead of repeated retries.
A repository is missing or disconnectedPermalink to A repository is missing or disconnected
Check the workspace
Select the workspace that owns the connection. A repository visible in a personal workspace is not automatically part of an organization.
Check access at the source
For GitHub, confirm the installation includes the repository. For GitLab and Bitbucket, confirm the authorizing account can access the project or repository.
Refresh the connection's repository list
Reconnect if the connection asks for attention, then refresh or sync and add the repository to Relane if it has not been imported.
Check repository state
An archived or disconnected repository may remain in history without being eligible for a new scan. Follow the repository's displayed action.
Authorization did not finishPermalink to Authorization did not finish
Start a fresh connection attempt from Relane rather than refreshing an old authorization result or reusing a callback URL. Complete consent with the account that can access the intended repositories. If you see an insufficient-permission message, review the requested consent and your source account's access; a different email address is not automatically required.
After authorizing, return to Repositories and confirm the connection and available repositories. A successful authorization alone does not add every repository or prove a scan has run. If the browser shows a response instead of returning to Relane, open the console and check the connection before repeating consent.
A scan stopped or produced limited coveragePermalink to A scan stopped or produced limited coverage
| What you see | What to do |
|---|---|
| An existing scan opens instead of a new one | Review the active scan for that repository; do not repeatedly submit the same assessment. |
| Completed with limited coverage | Read the stated limitation. Confirm the selected scope, address access or input issues, and use the recommended follow-up rather than calling the repository clean. |
| Time budget reached | Follow the displayed next step. A stopped or partial assessment is not a full result, and repeating an unchanged request may repeat the same limitation. |
| Temporary service or capacity problem | Follow the displayed wait or retry advice. Avoid repeated starts while the same condition persists. |
| Result not available | Read whether preparation is still in progress or a result cannot be recovered. Contact support for a terminal assessment with no recoverable result. |
A finding count or fix action is unexpectedPermalink to A finding count or fix action is unexpected
Check the scan, workspace, severity filter and triage state. Items that still need validation are separate from confirmed findings. Marking a finding as not a real issue or accepted risk changes how it is included in the confirmed list; it does not change the repository's code.
Prepare fix is available only for eligible findings. An open fix workspace does not guarantee approval: an unassessed or unsafe proposal, a changed diff, an old revision or a moved base can require a new review. Read the refusal reason and regenerate or reassess as appropriate rather than attempting to bypass it.
A schedule or notification did not runPermalink to A schedule or notification did not run
A saved schedule is not proof of execution. Check whether it is enabled, its UTC time, its last attempt and the repository's current scan eligibility. A saved destination is not proof of delivery: check the selected events and the most recent delivery receipt. Use the reported reason to distinguish a scan that never started from a notification that could not be delivered.
Get useful help without sharing secretsPermalink to Get useful help without sharing secrets
If sign-in is unavailable or registration is closed, use the access arranged during onboarding or contact Relane. If organization membership changed, switch to a workspace you belong to or ask an owner to review your invitation.
- Include the affected page, workspace name and the approximate time and timezone.
- Include the scan or report identifier and the non-sensitive error message when available.
- Describe what you expected and what happened, including whether a reconnect or fresh authorization was already attempted.
- Do not include tokens, full callback URLs, notification secret URLs or private source code in an initial support message.