Skip to main content

Troubleshoot Webhooks and Review Jobs

If you expected a merge request to be reviewed and saw no output, the problem is usually in one of these areas:

  • the GitLab event never reached Buzzbin
  • the event reached Buzzbin but was intentionally skipped
  • a Review Job was created but the run or publication failed later

Where to start​

Check these in order:

  1. open the repository's Webhook Deliveries page
  2. find the latest delivery related to the MR
  3. inspect the outcome or skip reason
  4. if a job exists, open Review Jobs and then the run detail page

Common skip reasons​

These are the most common causes of a skipped review:

  • the MR was still draft
  • only metadata changed and there was no new commit
  • Code Review or the relevant capability was disabled
  • the organization wallet had no available credit
  • the repository reached its daily run cap
  • the repository was inactive
  • for comment answers, the bot was not mentioned

If no delivery appears at all​

These scenarios are more likely:

  • the webhook was never created or later became unhealthy
  • the Project Access Token is no longer valid
  • the token's scopes or role changed
  • the GitLab host is not reachable from Buzzbin servers

If the connection worked before and later stopped, token rotation is usually the first useful fix. Buzzbin re-validates the token and repairs the webhook if needed.

If a review job exists but nothing was posted​

Review Jobs and run details tell you which state the job reached:

  • queued
  • in progress
  • done
  • failed

For failures, the run status and error details are the best source of truth. If the problem mainly affects older open MRs, use Review existing open merge requests for a more controlled preview path.

Do not forget this for comment answers​

Comment Answers are mention-gated. If you reply in a thread without calling the bot, Buzzbin usually does not enqueue an answer.

When to involve support​

If you checked the above and the issue continues, collect these details for the product or support team:

  • repository link or identifier
  • MR number
  • approximate event time
  • the visible reason or screenshot from Webhook Deliveries or Review Jobs