Skip to content

Resources

Troubleshooting

What to check when Codebot doesn’t review a pull request, or a run fails.

A pull request wasn’t reviewed

Look at the pull request’s checks first.

  • A skipped check: a skip rule matched, and the check says which. Comment @trycodebot review to review it anyway.
  • No check at all: Codebot didn’t receive the event, or the repository isn’t on.
    • Check that the repository is listed in Code review → Repositories.
    • Check that the pull request event is one you review in Code review → Triggers. For example, with only Opened selected, pushes don’t start a review.
    • On GitHub, check that the TryCodeBot app is installed on the repository.
    • On Azure DevOps, a repository marked Polling picks up changes within two minutes.
  • Pull requests from forks are skipped by default.
  • Your compute limit: when your plan’s included compute is used up, new runs are cancelled. See Usage and limits.

A run failed

Open the run from Activity or from the check’s link. The run page shows the error and the transcript up to the failure. Common causes:

  • No model, or the model’s key is gone. Pick a model again in Code review → Review or on the Agent page, and check Settings → Models.
  • The provider refused the request: an invalid key, no credit left, or a rate limit. The error shows the provider’s message.
  • Timeout. Reviews have about 20 minutes. On very large pull requests, add ignored files or split the change.

A failed review leaves its check neutral, so it never blocks a merge.

Mentions get no answer

  • Check that Take work when mentioned is on and the agent has a model, on the Agent page.
  • Check that the place you mentioned it is switched on under Where you can mention it.
  • On GitHub, only owners, members and collaborators can mention Codebot. Others get a 😕 reaction.
  • On Azure DevOps, mention the user whose token you connected, in a repository with code review on.
  • In Discord, the channel must be turned on, and you may need one of the roles allowed to ask.

The review isn’t on the lines I expected

Codebot anchors findings to lines the pull request changed. When the git host rejects a comment’s line (for example, after a force push moved it), the finding is moved into the review body instead.

Azure DevOps

  • Repository shows Polling: the token’s user can’t create service hooks. See Service hooks or polling.
  • Reviews stopped: the token probably expired. Use Replace token in Settings → Integrations → Azure DevOps.
  • Review command does nothing: commands need service hooks, so they don’t work on polled repositories.

Still stuck?

Email simone.priuli@icloud.com with a link to the run.