Skip to main content

FAQ and Common Errors

Why does repository connection fail?​

The most common causes are:

  • the repository URL is wrong or does not start with https://
  • the token is invalid
  • the api or read_repository scope is missing
  • the token role is lower than Maintainer
  • your GitLab host is not reachable from Buzzbin servers

If you see codes like REPO_TOKEN_INVALID, REPO_TOKEN_MISSING_SCOPES, or REPO_TOKEN_INSUFFICIENT_ROLE, the problem is usually in that area.

Why did GitLab show the token only once?​

That is normal GitLab behavior. After creating a Project Access Token, you need to copy and store it immediately. If you lose it, you usually need to create a new token or rotate the old one.

What happens if the token expires or is revoked?​

Repository connection or webhook operations may stop working. Rotate the token in GitLab and then update Buzzbin with the new value so the connection can be validated again and the webhook repaired if needed.

What if I cannot find the Access tokens page in GitLab?​

Usually one of these is true:

  • your project role is not high enough
  • your GitLab instance restricts project access token creation
  • your current plan has a relevant limitation

In that case, ask your GitLab administrator or project owner for help.

Why was my MR not reviewed?​

Check these first:

  • the MR was still draft
  • no new push happened and only metadata changed
  • Code Review is disabled in repo config
  • the wallet has no available credit
  • the repository reached its daily run cap
  • the webhook delivery never reached Buzzbin or later became unhealthy

For the exact reason, start with the repository's Webhook Deliveries and Review Jobs pages.

Why did Buzzbin not answer my comment?​

In the current behavior, Comment Answers are mention-gated. The note itself must contain @buzzbin. If you only replied in a thread without calling the bot, no answer is usually created. You also will not get an answer if Comment Answers is disabled for that repository or if the note is a system note.

Why does a backfill run still consume credit?​

Because the cost comes from running the model and processing the review. Backfill runs go through the same review and publishing path as a normal review, so it consumes credit the same way.

Why do two similar reviews not cost exactly the same?​

Cost depends on multiple factors:

  • the selected model
  • the number of tokens used
  • the USD-to-IRR FX rate at execution time
  • which review capabilities are enabled

So two visually similar MRs do not necessarily cost the same.

Are all findings posted?​

No. Buzzbin tries to avoid low-value noise. Low-confidence findings are generally not posted, and some categories may also be disabled by your review config.

Does Buzzbin keep our source code?​

Buzzbin does not keep repository source code as permanent product data. The clone exists only for the duration of a review run. For more detail, see Privacy and data handling.

How do I tell whether the problem is the webhook or review config?​

If you do not see a delivery at all in Webhook Deliveries, the issue is more likely with the webhook or token. If you do see a delivery but its outcome is a skip, the cause is more likely to be review config, draft state, or guardrails.