Docs / Troubleshooting your workspace

ShipGlance is free. Sign in with GitHub, install the App, and your board is live. Sign up free →

Troubleshooting your workspace

What the warnings in Settings and Insights mean, and what to do about each. Most fixes happen in your GitHub App installation, followed by a retry in Settings.

The last sync failed

The Settings overview shows when your repositories were last read from GitHub. If that sync failed, a red message says why. A failed sync does not change your board: it keeps the setup it already had. The common causes:

• GitHub refused access. The message says GitHub denied a request, could not find something, or that the setup names a repository outside what the App can see. Usually the App was removed, suspended, or no longer has that repository selected. Open the App's installation on GitHub (your account or organization settings, under GitHub Apps), make sure it is active and that the repository is selected, then come back and choose Re-run discovery.
• A repository has too many workflows. The message says discovery stopped and names a repository with more workflows than the 100 we read per repository. GitHub's count includes disabled workflows too. The sync stops rather than showing a board with workflows missing. Remove workflows you no longer use from that repository (GitHub may keep listing a deleted workflow file while its past runs remain), or deselect the repository in the App installation on GitHub, then re-run discovery.
• Too many repositories. The message says discovery stopped with "too many installation repositories": the installation has more than the 2,000 we read. Choose specific repositories in the App installation on GitHub instead of all of them, then re-run discovery.
• GitHub was busy or unreachable. Rate limits and GitHub outages clear on their own. Wait a few minutes and re-run discovery.
• The board could not be updated. Your repositories were read, but the new setup could not be applied. The previous setup stays in effect. Re-run discovery; if the same message comes back, report it.

Any member of the workspace can re-run discovery. If your configuration is managed in code, the button reads Re-sync config from code instead — see configuration.

The repository list could not be loaded

The repository picker in Settings → Repositories lists what the GitHub App can see. When that list cannot be loaded, a message names the account or organization and the reason.

• GitHub access. The App may have been removed or suspended, or GitHub may be briefly unavailable. Check the installation on GitHub, then reload the page.
• Too many repositories. An installation with more than 2,000 repositories is refused rather than listed partially. Select specific repositories in the App installation on GitHub, then reload the page.

A failed list is not remembered, so reloading reads it from GitHub again. A list that did load is remembered for a few minutes so Settings opens quickly; Refresh from GitHub reads it again. Only the workspace owner can choose which repositories appear on the board.

The board health warning

The Settings overview shows your board's health and when it was last checked. A red warning means the board is running but its last check did not pass. While that lasts, the board may be unavailable or showing older data. It can be a short blip, for example right after a change to your setup; it can also mean the board could not refresh its access to GitHub.

• Health is re-checked automatically. Wait a minute and reload Settings — a short blip usually clears by itself.
• Check that the GitHub App is still installed and not suspended, then choose Re-run discovery.
• If the warning stays, report it. The report includes the health Settings shows, so there is nothing to copy.

Setup did not finish

After you connect GitHub, a setup page reads your repositories, builds your board and starts it, updating as it goes. If it stops with an error, or stops updating, a Retry setup button appears.

• Retry first. Interruptions and "busy" messages usually succeed on a second try.
• Check the installation. Make sure the GitHub App is installed on the account or organization you connected, is not suspended, and has at least one repository with GitHub Actions workflows selected. If GitHub access is being checked again after a change on GitHub, the page says so — look at your connections in Settings and retry.
• "Nothing to monitor yet" is not an error: GitHub is connected, but no selected repository has workflows. Add a workflow or select more repositories on GitHub, then retry. If the message says no repositories are selected for display, the board is set to show only selected repositories and none are chosen: pick some under Settings → Repositories.
• If setup keeps failing, report it from the setup page.

Insights shows nothing yet

Insights is worked out from the history your board records as your workflows run — nothing is estimated. The page names the window it covers at the top. It reads "Not enough history yet" when that window has neither of these:

• A successful deploy. Only stages marked as deploys count. A job with a GitHub environment: is a deploy stage automatically; otherwise mark it in Settings — see how deploy stages are found.
• Two or more finished runs of the same workflow (passed or failed), which is what flakiness needs to compare.

A new workspace starts with no history, so Insights fills in as your workflows run over the following days. How far back history reaches depends on your plan; if a longer window is not included, Insights says so on the page. If Insights says it is not enabled, history is not being recorded for your board — report it.

Insights could not load

Insights is worked out from your board's recorded history each time you open it. "Could not load insights" means that did not come back this time — for example because your board was restarting, could not be reached for a moment, or could not read its history just then. Opening Insights only reads; it does not change your workflows or your board.

• Choose Retry. A short interruption usually clears within a minute.
• If the board itself also shows a warning, deal with that first — see troubleshooting the board.
• If Insights keeps failing while the rest of the board works, report it with Need help? on that page. The report says that Insights failed to load, so there is nothing to copy.

Still stuck?

Use Report a problem in the app (in the sidebar, or Need help? next to most errors). It attaches the details of what you were looking at, and shows you exactly what is sent first. Or email [email protected].