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 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 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, 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, 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. |
| â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. |
| 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. |
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. |
| 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. |
| 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, 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. |
| â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. 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 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. |
| 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
Set up Verify
Prepare an environment and check the repositoryâs settings.
Results and bugs
Read outcomes and evidence in detail.