Limits and caps

Review caps

Angada limits reviews within a rolling 24-hour window:

Workspace policy can set a workspace-wide cap. If a review is skipped after the pull request cap has not been reached, ask a workspace admin to check whether a workspace cap applies. Manual re-runs remain subject to both caps.

The 150-file ceiling

Automatic reviews are blocked when a pull request has more than 150 changed files. A manual re-run can bypass this file limit, but review caps still apply. See Re-runs and continuity for the available ways to request one.

Other reasons a review may be skipped

These conditions can prevent an automatic review from starting:

• Draft pull requests are skipped by default until marked ready for review.
• Bot-authored pull requests are skipped by default. A Review Seat can override the bot default.
• Unseated authors are not eligible for review. See Review Seats for how seats affect review access.

Push timing

Angada waits 90 seconds after a push before starting a review. If more commits arrive during that window, Angada reviews the latest pull-request head after the burst.

When you hit a cap

When a review cap prevents a review, the check reports Skipped. A manual re-run does not bypass review caps. Wait until the cap window has room, then request a re-run if the pull request still needs a review.

Changing the caps

Workspace admins can view and change the per-pull-request cap in Settings → Review. See Review settings for the controls available there.