Troubleshoot a review
Recover from a missing, skipped, blocked, or unexpected Angada review.
Start with the Angada check on the pull request. Its state tells you whether Angada is waiting, skipped the review by policy, or could not review the current change.
No review starts after a push
Confirm the repository remains in the GitHub App installation's repository access. Angada waits 90 seconds after a push, so wait for the debounce window before treating a review as missing. Draft pull requests are skipped by default until someone marks them ready for review.
The check says skipped
Angada skips a review when the pull request does not pass its trigger policy. Common causes are a draft pull request, a bot author, no eligible Review Seat, or a rolling review cap. The check stays visible so the result is not mistaken for a completed review.
Use Review settings to confirm draft behavior and Limits and caps for the current cap rules.
The review is blocked
Automatic review stops at 150 changed files. A user with write access can request a manual re-run for a larger pull request, subject to the rolling caps. Split the change when you can: a smaller pull request gives reviewers and the review more focused evidence.
A finding looks wrong
Dismiss the finding and include the reason when the interface offers it. The outcome carries forward when Angada recognizes the same issue after a push. The evidence link lets you compare the claim with the exact file and line range Angada reviewed before you decide.
The check is no longer current
Pushes supersede older review work. Open the check for the latest head and wait for the current review to finish. See Re-runs and continuity for how Angada updates matching findings and comments.
Need more help?
Send the pull-request URL and check state to Angada support. Avoid including source code in the first message unless the support team asks for it.