Skip to main content
Find your symptom below, then follow the check and fix. Most problems come from four places: the pull request (PR) or merge request (MR) itself, the repository’s settings in CloudThinker, the webhook, or the Git provider credentials.

​
Start here: what’s on the PR?

And in CloudThinker:

​
No comment on a new PR

CloudThinker posts a progress comment within moments of a PR opening, then replaces it with the summary. If nothing appears at all, CloudThinker either never heard about the PR or chose to stay silent.
1

Check the PR isn't a draft

Draft PRs and MRs aren’t reviewed. Mark the PR ready for review and CloudThinker picks it up. (AWS CodeCommit has no drafts, so this doesn’t apply there.)
2

Check the repository is selected

Open Review → Settings → Repositories and find the repository. Its Review switch should be on. If it isn’t listed, add it. If it shows Cloning, the first clone is still running.
3

Check the webhook (GitLab, Azure DevOps, AWS CodeCommit)

GitHub and Bitbucket register webhooks for you. The other three need one you add by hand, and a missing or wrong one is the most common cause of silence.Open the webhook’s delivery history in your provider:What the history tells you:
  • No deliveries: the webhook is missing or lacks the trigger. Re-add it with the URL, secret token and triggers from Configure webhooks.
  • Failed with 403 “Repository is not enabled for Review”: turn on the repository’s Review switch in Review → Settings → Repositories.
  • Other 4xx failures: the URL or secret token doesn’t match. Copy both again from the setup wizard and update the webhook.
  • 5xx failures: CloudThinker couldn’t process the event. Redeliver it from the delivery history. If it keeps failing, contact support (see Still stuck).
  • Successful deliveries but still nothing: go to the next step.
4

Start the review by hand

Comment on the PR:
On AWS CodeCommit there’s no review comment command, so push a new commit to the PR’s source branch instead.Success state: a CloudThinker progress comment appears on the PR. If it doesn’t, check Provider auth errors.

​
Skipped reviews

When CloudThinker decides not to review a PR, it says so in a CloudThinker Code Review Skipped comment. The second line tells you why.
The skip marker @cloudthinker:ignore is case-sensitive and works anywhere in the description. Use it for one-off PRs. For whole groups, such as every PR from dependabot[bot] or every PR into release/*, use a filter instead. See skip a review.
A skipped PR still shows up under Review → Reviews with the Ignored verdict, so you can confirm what happened without opening the provider.

​
Reviews that stop or fail

Findings posted before a stop stay valid. You only lose the summary. On AWS CodeCommit the review comment command isn’t supported, so push a new commit to the PR’s source branch instead, or re-run from Review → Reviews. See provider support. You can also restart from CloudThinker: open the PR in Review → Reviews, then click Re-run review in the ⋯ menu. While a run is still going, that menu shows Stop review in its place, so wait for it to end or stop it first.

​
Re-review a PR

Pushing new commits to an open PR starts an incremental review on its own: only the new changes are read. To re-review without pushing, comment:
@cloudthinker-ai review again, @cloudthinker-ai continue and @cloudthinker-ai continue review do the same. All of them continue from the last reviewed commit. There’s no command for a full review from the first commit. For a deeper pass over the latest commit, comment @cloudthinker-ai review ultra (see Ultra review). If Ultra is off for your installation, the bot replies Ultra review is turned off for this installation. On AWS CodeCommit that command isn’t supported: push a new commit to the PR’s source branch to review it again.
The command must be the whole comment. @cloudthinker-ai review this file carefully is read as a question, not a re-review, so you get an answer instead of a new review.

​
Mention commands get no reply

​
Provider auth errors

When the Git provider rejects CloudThinker’s credentials, the Review page header shows Reconnect your Git provider, with an Authentication Error alert. Reviews stop until you fix it. Your repositories and settings are kept. GitHub has no token to update, because it uses the CloudThinker GitHub App. If GitHub reviews stop, the app was uninstalled or lost access to the repository: reinstall it, or add the repository in the app’s settings on GitHub. Installing it on a GitHub organization is done on GitHub by an owner of that organization, not by a CloudThinker role. Success state: the Review page loads normally. Comment @cloudthinker-ai review on any PR that opened while the connection was down. On AWS CodeCommit, push a new commit to its source branch instead. The token scopes for each provider are in Provider authentication. The usual reasons a new token fails:
  • GitLab: the token’s role is below Developer, or it lacks the api scope. Guest and Reporter can’t comment on MRs.
  • Azure DevOps: the personal access token (PAT) expired. PATs expire on the date set at creation, so note it and replace the token before then.

​
Repository problems

In Review → Settings → Repositories, a row under the repository name can show: When none of these apply, the row shows the default branch. The Review switch in the same row turns reviews on or off, and the Learnings column can show Paused while Review is off (see Learnings).

​
Findings are wrong or noisy

​
Other Review features

​
Still stuck

Collect the workspace name, the repository, the PR link, the provider, the time you opened the PR and the text of any CloudThinker comment. Then email support@cloudthinker.io. The general troubleshooting page covers problems outside Review.

​
Next steps

Mention commands

Every command the review bot understands, and where each provider supports it.

Provider authentication

Token scopes and webhook steps for each Git provider.