## TL;DR

The CodeRabbit check is stuck in pending  -  usually the app is backlogged, the webhook was missed, or the PR is too large. Check the app status, then re-request the review or push an empty commit to retrigger.

## Error

```text
CodeRabbit  -  Review pending for 45 minutes (expected < 5).
```

## Steps

1. Check CodeRabbit's status page / app health for an ongoing incident. Expected: you know whether it is a global outage.
2. On the PR, look for the CodeRabbit comment or check run  -  a stuck run often shows no logs at all. Expected: confirmation the review never started.
3. Retrigger: push an empty commit, or remove and re-add the CodeRabbit app / re-request review. Expected: a fresh review starts.
4. If it stays stuck, ask an admin to skip the required check for this PR and file a report with CodeRabbit support.

## When to use

- The CodeRabbit check stays pending far past its normal time.
- The PR otherwise meets merge requirements.

## When not to use

- CodeRabbit completed with findings you disagree with  -  reply to the findings instead.
- The check failed fast with an error; read the error, this is a different problem.

## Tool compatibility

- CodeRabbit AI review app.
- GitHub / GitLab.

## Variant phrasings

### Pending only on huge PRs

Split the PR  -  oversized diffs queue longer and time out more.

### Pending after a force-push

The app may still be analyzing the old SHA; retrigger explicitly.

## Why it happens

A pending check that never resolves blocks required-check gates indefinitely. Retriggering creates a fresh analysis run; if the backend is wedged, only the vendor or an admin override unblocks the PR.

## Edge cases

- Do not make required-check overrides a habit; track how often the app stalls before deciding to keep it required.
- Empty commits to retrigger pollute history  -  prefer the app's re-request control when available.

## Provenance

Resolved from the public thread: https://vectle.com/posts/pst_QCoXJaL8ScP9KoRYW9pm6w