Troubleshooting

No review on a pull request#

• It’s a draft. Drafts aren’t reviewed. Mark it ready for review (the GitHub App reviews it then), or push a commit after.
• The App can’t see the repository. On GitHub, open Settings → GitHub Apps → Audit Bench Ai → Configure for the account or organization and check the repository is selected.
• Automatic review is off. In Repository scan, check the switch on the installation (GitHub App) or the webhook (GitLab, Bitbucket, GitHub webhook).
• The installation isn’t linked to your account. If you installed the App from GitHub directly, open Repository scan and claim it.
• A bot opened the pull request. Pull requests from bots such as Dependabot are skipped.
• That commit was already reviewed. Each commit is reviewed once. Click Re-run, or push a new commit.

“Review didn’t finish”#

The check closed as neutral with a reason:

“Couldn’t review this commit because of a temporary problem”#

Usually a dropped connection to GitHub or the AI provider. Click Re-run on the check, or push a new commit. If it keeps happening on the same pull request, tell us the repository and pull request number.

“Skipped the automatic review of this commit”#

You’ve reached a plan limit, or the account doesn’t have access to the repository. The message gives the reason. See Plans and limits.

GitLab or Bitbucket webhook not firing#

• Check the webhook’s recent deliveries in GitLab or Bitbucket. A 403 means the secret doesn’t match: delete the webhook in Audit Bench Ai, create a new one and paste the new secret.
• On GitLab, the repository identifier must be the numeric project ID, and Merge request events must be ticked.
• On Bitbucket, the identifier is workspace/repo-slug, with the Pull Request: Created and Updated triggers.
• Check your access token hasn’t expired. The app asks for a new one if it has.

Too many comments#

• React 👎 to findings you don’t want; after a couple, that kind of finding stops in that repository.
• Raise the minimum confidence and turn off optional suggestions in strictness.
• Add an Ignore files rule for generated code, or a Don’t flag rule for a convention your team has decided on.

A finding is wrong#

Reply to it with the reason. Audit Bench Ai rechecks the code and withdraws the finding if you’re right. See Replies and reactions.

The check isn’t offered in branch protection#

GitHub only lists checks it has seen in the last week. Open a small pull request, wait for the Audit Bench Ai check, then add it. See Make it a required check.

Still stuck?#

Contact us with the repository, the pull request link and what you expected. We read every message.