Bugbot cannot run

Support Help
,
27

However, there is no individual billing access for BugBot.

image
image3840×1984 179 KB

28

Was it already activated previously or this is the first time your seeing this? It might be working now!

29

Still not working

image
image2052×1076 130 KB

30

Worth pinging @deanrie then

31

@deanrie Please help

32

Hey, good news: based on the screenshot, Bugbot is now Active (usage-based, billed through your Cursor plan), so the old issue with running out of free-tier reviews is fixed, and your entitlement looks good.

One thing is still left. In the PR screenshot, the bugbot run comments are being posted by the Mercaso-Bot account, not your personal GitHub account. Bugbot doesn’t trigger on comments from bot or app accounts, so you won’t see any response.

Try this:

  • Post bugbot run (or cursor review) as a new top-level PR comment from your personal GitHub user (the one linked to Cursor via https://cursor.com/dashboard/integrations), not via a bot.
  • Make sure the right repo is enabled in Bugbot > Repositories.

If Bugbot is still silent after you run it from your own account, share the PR link and the Request ID from the bugbot run verbose=true response, and I can check the logs for that specific run.

33

Hi, I’ve come across a similar situation, bugbot review wouldn’t start with manual trigger. I’m using the same account to trigger review as what I’ve used to connect to GitHub with. I’ve reset the GitHub connection, still the same issue. Bugbot is active with usage-based billing, and I’m on Pro subscription. No bugbot type usage exists in the ‘Usage’ tab.

One of the problematic runs:serverGenReqId_b54e3756-841d-4554-b1fa-d0cff78b3a8a

Any help is appreciated.

34

@Vertirax your case is different from the original one in this thread. The thread author had already used up their Bugbot free tier quota, but you already have Bugbot Active with usage-based billing, so the cause is definitely different and it’s better to debug it separately.

Please start a new thread so we don’t mix it with this one, and include:

  • a link to the PR where you triggered the review, and which provider it is GitHub / GitLab / Bitbucket
  • the exact trigger comment text and the output of bugbot run verbose=true it will include a fresh Request ID
  • a screenshot from Bugbot > Repositories showing whether the right repo is enabled

I’ve already seen Request ID serverGenReqId_b54e3756-841d-4554-b1fa-d0cff78b3a8a. Once you open a new thread, I’ll check the logs for that specific run.

35

Thanks, will do

36

nopes i am connected in cursor integration and MCP but bugbot not showing any repo

image
image928×108 2.84 KB

37

Hey @gourav.bhalla, from your screenshot I can see Bitbucket Cloud is connected correctly (Connected as “Gourav Bhalla”), so the integration looks fine. The fact that Bugbot > Repositories doesn’t load any repos even though Bitbucket is connected is a known bug on our side. I can’t share an ETA for a fix yet.

To avoid mixing this with the original request in this thread (it’s about a different cause), please start a separate thread for your case and include:

  • a screenshot of Bugbot > Repositories showing the empty list
  • whether you’re using Bugbot as an individual or as part of a Team, if it’s a Team, share the Team ID

This will help me link your case to the right issue and add repro details. Once you’ve created it, send the link and we’ll take it from there.