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

# A review failed or was incomplete

> What the rapid-review check says when a review couldn't finish or couldn't review every part of the change, and what to do; read this when the check says Review failed, Review incomplete, or Not reviewed with a cause such as the review service being unavailable or busy.

## What does "Review failed" mean?

"Review failed: …" means the review couldn't finish. The check's summary gives the cause and says to re-run the check to try again.

## What does "Not reviewed" or "Review incomplete" mean after a review started?

* **"Not reviewed: …"** after a review started: no part of the change could be reviewed.
* **"Review incomplete, no findings: …"**, or a findings title that ends with "units not reviewed: …": some parts of the change were reviewed and some weren't.

Under "What failed", the check lists each cause with how many parts of the change ("units") it affected, and says "Re-run this check to review what is missing." Parts that a backup model reviewed instead are listed there too.

If the check says some units weren't reviewed because the run's budget was spent, the review reached its cost limit before it reviewed every part.

## What causes can the check give?

The check names one of these causes:

* the review service is not available at the moment;
* the review service was busy;
* the review service was unavailable;
* the review service could not be reached;
* the review took too long;
* a request to the review service failed;
* the review returned no answer;
* the review's answer could not be read;
* a call to GitHub failed;
* GitHub rate-limited the app's calls;
* an unexpected error.

The check shows no more technical detail than this.

## What should I do when a review failed or was incomplete?

Re-run the `rapid-review` check on GitHub, or comment `@rapidreview-dev review` on the pull request. Parts that an earlier review already reviewed unchanged aren't reviewed again, so a re-run mostly reviews what was missing.

A review interrupted on Rapid Review's side is retried automatically, up to three times.

## Why is the check red?

A red `rapid-review` check means the review reviewed nothing because the review service couldn't be used (it refused the requests, was unavailable or busy, couldn't be reached, or didn't answer in time), or the review stopped and couldn't finish. If your branch protection requires the check, a red check blocks merging until a re-run reviews the change.

A review that reviewed only part of the change ends green, and so does one that reviewed nothing for another cause, such as answers that couldn't be read. Its summary says what it left out.

## Where else does a failed review show?

* **The summary comment** says the review couldn't finish and that its check says why.
* **The Rapid Review app** shows how each push's review ended, with the same cause: Reviewed, Partly reviewed, Not reviewed, Failed, Cancelled or In progress. Cancelled means a newer push replaced the review, or a restart cut it off.


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