DocsGetting Started
Troubleshooting
What each skip, status and error message means, and how to fix it.
Most problems show up as a status on the pull request or a message on the dashboard. Find the message below to see what caused it and how to fix it.
No review appeared#
| Situation | Why | What to do |
|---|---|---|
| The pull request is a draft | Drafts aren't reviewed. | Mark it ready for review. |
| AI review is off for the repository | The repository was turned off. | An admin turns on AI review in Repository Settings. |
| The repository isn't connected | It isn't covered by the installation. | On GitHub, add it to the Solemly App's repositories. On GitLab, make sure the token can see the project. |
| You just pushed again | When several commits are pushed in quick succession, Solemly waits briefly and reviews the latest. | Give it a minute. |
A @solemly comment got no reply | Only people with write access can run commands. Other comments are ignored without a reply. | Ask someone with write access, or check your permissions on the repository. |
Skipped reviews#
When Solemly decides not to review a commit, it still posts a status so the pull request isn't left waiting. On GitHub this is a neutral Review skipped check. On GitLab and Bitbucket it's a successful status reading "Solemly review skipped - comment @solemly review to run it". A skipped review never blocks a merge.
| Message | Cause | Fix |
|---|---|---|
| Skipped: this repository is set to review on request only. | The repository's Review when setting is On request. | Comment @solemly review, or change the setting. |
| Skipped: this pull request was already reviewed (review once). | Review when is Once per PR, and this pull request already has a review. | Comment @solemly review full to review again. |
| Skipped: automatic reviews are paused on this pull request. | Someone commented @solemly pause. | Comment @solemly resume, or @solemly review for a single review. |
| Skipped: the Solemly trial has ended. | The 14-day trial is over. | Choose a plan on the Billing page. |
| Skipped: the Solemly trial's 50 PR reviews are used up. | The trial's review limit was reached. | Choose a plan on the Billing page. |
| Skipped: this workspace has used its N PR reviews for this month. | The plan's monthly reviews are used up. | Add seats, or wait for the date in the message. Pull requests already reviewed this month keep being reviewed. |
| Skipped: this … already had its Solemly free trial in another workspace. | Each GitHub account, GitLab user or Bitbucket workspace gets one trial. | Choose a plan on the Billing page. |
| Skipped: this workspace's Solemly Standard plan ended on … | The paid plan ended. | Choose a plan on the Billing page. |
| Skipped: the Solemly plan has lapsed … | A payment is overdue or a renewal is due, and the 7-day grace period has passed. | Renew on the Billing page. |
See Plans & Usage for how reviews are counted.
Check and status messages#
| Message | Meaning |
|---|---|
| Review complete | The review finished and was posted. |
| Blocking: N high-severity finding(s) | The review found HIGH or CRITICAL issues and the repository blocks on them. Fix them and push, and the review runs again. |
| Superseded | A newer commit was pushed, so this review was dropped in favour of the newer one. |
| Review unavailable | Solemly couldn't complete the review. It doesn't block the merge. Push again or comment @solemly review. |
| Pull request too large | The change is too large to review in one go. It doesn't block the merge. Splitting the pull request helps. |
| Security scan not run | No security-relevant changes were found, so the security review didn't run. |
| No linked Jira ticket | No ticket key was found in the branch, title or description, or the ticket couldn't be read. See Jira. |
| Incomplete vs. KEY | The pull request doesn't yet do everything its Jira ticket asks. The missing items are listed. |
Solemly fails open: when something goes wrong on Solemly's side, the check reports a neutral or successful result so your merge isn't blocked by an outage.
Connecting a code host#
GitHub#
| Message | What to do |
|---|---|
| This GitHub installation is already connected to another Solemly workspace. | Disconnect it in the other workspace first. |
| The GitHub account that finished this can't see every repository the installation covers. | Ask an owner of the GitHub organization to finish connecting. |
| That GitHub link has expired or was already used. | Start again from the Repositories page. |
| GitHub sign-in was cancelled, so the installation wasn't connected. | Start again and approve the request. |
| This workspace is already connected to another source control provider. | A workspace connects to one code host. Disconnect the other one, or use another workspace. |
| Couldn't check the installation with GitHub. | Try again in a moment. |
If your organization requires admins to approve GitHub Apps, the install waits until an owner approves it on GitHub.
GitLab#
| Message | What to do |
|---|---|
| GitLab rejected the token | Check the token is valid, not expired, and has the api scope. |
| Connected, but couldn't auto-register any webhook. | The token needs the Maintainer or Owner role to manage webhooks. Reconnect with a group token, or add a project webhook manually. |
Bitbucket#
| Message | What to do |
|---|---|
| This Bitbucket workspace is already connected to another Solemly workspace. | Disconnect it in the other workspace first. |
| The Bitbucket account you confirmed with isn't an owner of the workspace Solemly was installed on. | Ask a workspace owner to connect it. |
| Bitbucket didn't tell us about this install. | Install Solemly again, starting from Solemly's Repositories page. |
| That Bitbucket link has expired or was already used. | Start again from the Repositories page. |
Signing in#
| Message | What to do |
|---|---|
| This email already has a Solemly account that signs in a different way. | Sign in with the method you used when you signed up. |
| Your account isn't part of a workspace yet. | Ask your workspace admin to invite you. |
| Your sign-in link expired. | Start the sign-in again. |
Still stuck?#
Email support@solemly.com. Every email reaches an engineer, and we reply within one business day. If it's about a review, include the pull request link: we can look at the exact diff that produced it. Signed-in users can also use the Support page in the app, which attaches your workspace details.
Something missing or unclear? Tell us.