> ## Documentation Index
> Fetch the complete documentation index at: https://docs.coderabbit.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Troubleshoot CodeRabbit Verify

> Fix Verify runs that don't start, get skipped, wait for capacity, or end blocked, inconclusive, or without evidence.

GitHub Cloud (Verify is available on GitHub Cloud. GitHub Enterprise Server is not supported.) GitLab.com (Verify is available on GitLab.com. GitLab self-managed is not supported.) Bitbucket Cloud (Verify is available on Bitbucket Cloud. Bitbucket Data Center is not supported.) | Cloud Only (This feature is available on CodeRabbit Cloud only. It is not available on self-hosted CodeRabbit deployments.) Open Beta (Verify is in beta and free during the beta.)

## Starting a run

| What you see | What to do |
| - | - |
| Nothing happens after you post `@coderabbitai verify` | Post the command as a new comment on the pull request. A reply in a review thread is ignored. If a new comment also does nothing, check that the repository is on GitHub Cloud, GitLab.com, or Bitbucket Cloud, and that **Verify** appears in your CodeRabbit app's sidebar. Verify isn't available for your organization otherwise. |
| "This command requires write access to the repository. Only users with write or admin permissions can trigger CodeRabbit to commit or create pull requests." | You need write access to the repository in your Git provider. Ask a maintainer to grant it, or to post the command. |
| "CodeRabbit could not verify your permissions on this repository, so this command was not run." | Your Git provider didn't confirm your access. Retry in a few minutes. On Bitbucket, connect or reconnect your own Bitbucket account in CodeRabbit. If it keeps happening, contact [CodeRabbit support](https://docs.coderabbit.ai/support) with a link to the comment. |
| "CodeRabbit Verify requires verified access to the GitLab organization." | Ask a GitLab organization administrator to review your membership. |
| "CodeRabbit chat interactions are restricted to organization members for this repository." | On GitHub, the repository's configuration sets [`chat.allow_non_org_members`](https://docs.coderabbit.ai/reference/configuration#param-chat-allow-non-org-members) to `false`, and you aren't a member of the organization. Ask an organization member to post the command. |
| "CodeRabbit Verify cannot start because this repository is not enabled for PR Verify. Enable PR testing in Verify settings." | The repository hasn't been added to Verify, or **Enable PR testing** is off. Select the **Verify settings** link in the reply, or [add the repository](https://docs.coderabbit.ai/verify/setup.md#add-a-repository), then post the command again. |
| "CodeRabbit Verify cannot read this pull request's source commit in Bitbucket." | Check that the source repository and commit still exist, and that the CodeRabbit bot has read access to the source repository. Then retry. |
| "Verify is already testing the current PR head." | A run is already testing this commit. Follow **View running test**, or wait for it to finish. To run with different instructions, wait for the run to finish or [stop it](https://docs.coderabbit.ai/verify/pull-requests.md#stop-a-run), then comment again. |
| "Verify testing was intentionally skipped under the PR testing criteria. This is not a failed test result." | The selection rules excluded this pull request from automatic runs. To test it anyway, comment `@coderabbitai verify`. To change which pull requests qualify, edit the [selection rules](https://docs.coderabbit.ai/verify/pull-requests.md#selection-rules). |
| "Verify was cancelled before testing started because a new commit was pushed. Automatic runs on new commits are disabled for this repository." | **Also verify new commits** is off, so the automatic run for the earlier commit was cancelled and no run started for the new one. Comment `@coderabbitai verify` to test the latest commit, or turn on **Also verify new commits** in the repository's [Verify settings](https://docs.coderabbit.ai/verify/setup.md#repository-settings). |
| No automatic run on a pull request | Check that **Enable PR testing** and **Auto Verify** are on, and for new pushes, **Also verify new commits**. Automatic runs skip draft pull requests, pull requests opened by bots, closed and merged pull requests, and public GitHub repositories. Marking a draft ready for review or reopening a pull request doesn't start a run. Comment `@coderabbitai verify`, or push a commit with **Also verify new commits** on. |
| The **Run verifier** dialog says "A verifier is already queued or running for this branch and environment." | You can't start another run on that branch and environment until the active one finishes. Wait for it, or open it and select **Stop run**. |
| A schedule's **Occurrence history** shows a skipped or failed occurrence | Read the reason next to it. A common one is "Another Verify run was active on this branch and environment.": scheduled occurrences are skipped, not queued, while another run is active. See [Occurrence history](https://docs.coderabbit.ai/verify/user-journeys.md#occurrence-history). |

## Setup and access

| What you see | What to do |
| - | - |
| **Verify** isn't in the CodeRabbit app's sidebar | Verify isn't available for your organization. It requires CodeRabbit Cloud with GitHub Cloud, GitLab.com, or Bitbucket Cloud. If those apply, contact [CodeRabbit support](https://docs.coderabbit.ai/support). |
| **Access needed for Verify setup** | You lack a permission the page needs, often the Coding Agent write permission. Users with the Billing Admin role can't use Verify. Select **Copy access request** and send it to a workspace administrator, then select **Check access again**. See [Permissions](https://docs.coderabbit.ai/verify/access-and-billing.md#permissions). |
| **No ready environment for this repository**, **Environment needs preparation**, or no environment to select | Verify only offers environments that are ready and prepared for the repository. Assign the repository to an environment and prepare it in [Coding environments](https://docs.coderabbit.ai/code/environments.md), then select **Refresh environments**. |
| "This environment is no longer ready. Refresh its status or choose another ready environment before adding the repository." | The environment changed or is being prepared again. Select **Refresh readiness**, or choose another ready environment. |
| "You need an assigned Review seat to manage environments. Ask a workspace administrator to assign you one." | Preparing environments requires an organization admin with an assigned Review seat or an active trial. Ask a workspace administrator to assign you a seat, or to prepare the environment. |
| "Enable data retention in organization settings to use Coding Agent." or "Coding Agent is not enabled for this organization." | Environments need Coding Agent enabled for your organization, including data retention. Ask an organization admin to turn on data retention in the organization settings. If that doesn't help, contact [CodeRabbit support](https://docs.coderabbit.ai/support). |
| "A repository supports up to 50" | The repository's journey library is full. Delete journeys you don't need before adding more. |

## Run results

| What you see | What to do |
| - | - |
| **Outdated run** or **Superseded** | The run was stopped, or a newer run or commit replaced it. Its results apply only to the commit it tested. Read the latest run. To test again, comment `@coderabbitai verify` on a pull request, or select **Run tests** on the repository's **Journey Testing** > **User journeys** page for a user journey run. |
| "Waiting for sandbox capacity" with a timer | Verify is waiting for a free sandbox. The run starts when one is available. |
| "Sandbox capacity unavailable after 15 minutes." | No sandbox became available in time. Start a new run later. |
| "Verify exceeded its run limit and cleanup grace." or "Verify could not complete before its run deadline." | The pull request run took longer than Verify allows. Make the startup script start the app faster. Instructions after `@coderabbitai verify` can't narrow a run that has saved scenarios, because every saved scenario runs; delete scenarios you don't need on the pull request's **Verify** tab in Change Stack. Then run it again. |
| **Blockers** or **Testing blocked** | Missing prerequisites limited testing. Open the blocker and read its **Impact** and **Suggested remediation**. Typical fixes: add the credentials as environment variables or secrets, seed test data in the startup script, and describe the test account in the [test instructions](https://docs.coderabbit.ai/verify/setup.md#write-test-instructions). Then run again. |
| **Blocked** or **Testing error** | An execution, setup, or infrastructure error stopped testing. Check that the environment is prepared and that its startup script starts the app. Run again. If it keeps failing, contact [CodeRabbit support](https://docs.coderabbit.ai/support) with a link to the run. |
| "QA action budget exhausted; 3 of 5 scenarios completed." or a similar budget message | The run used up its budget before every scenario finished. Results for the completed scenarios are kept. Reduce or split what the run must cover, then run again. |
| Blockers say the app couldn't be reached | Make the startup script start the app inside the sandbox, and give the starting URL, such as `http://localhost:3000`, in the test instructions. See [Prepare an environment](https://docs.coderabbit.ai/verify/setup.md#prepare-an-environment). |
| **Inconclusive** or **Results inconclusive** | Verify couldn't establish a reliable result. This isn't a pass. Read the scenario's limitations for missing prerequisites or evidence, fix them, and run again. |
| **Skipped** | Verify found no behavior to test in the change. This isn't a pass. If the change does affect behavior, comment `@coderabbitai verify` with instructions naming what to check. |
| "No evidence captured for this run." or "Evidence will be available when this run finishes." | If the run is still active, wait for it to finish. Otherwise read the scenario's limitations. Don't read missing evidence as a pass. |
| "This recording is unavailable for the selected Verify run. View the Verify results for available evidence." | Open the run's results and use its screenshots and text evidence instead. A note such as "Session video is partial." explains what was recorded. |

## What's next

> [card] [Set up Verify](https://docs.coderabbit.ai/verify/setup.md)
>
> Prepare an environment and check the repository's settings.

> [card] [Results and bugs](https://docs.coderabbit.ai/verify/results.md)
>
> Read outcomes and evidence in detail.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.