Bugbot not able to run in Gitlab after increasing usage limit

Support Bug Reports
, ,
1

Where does the bug appear (feature/product)?

Bugbot / Security Review Agent

Describe the Bug

We hit our Cursor on demand usage limit and increased it. However, Bugbot is still giving this message, even after increasing the usage limit:

“Bugbot couldn’t run - usage limit reached
Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.
A user or team admin can review and increase usage limits in the Cursor dashboard.
(requestId: serverGenReqId_8b7aadcd-1175-4b7e-850c-562b38afc9d6)”

Cursor chat still works.

Steps to Reproduce

Comment “bugbot run” on a Gitlab MR, see this message after hitting the usage limit and then increasing the limit:

“Bugbot couldn’t run - usage limit reached
Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.
A user or team admin can review and increase usage limits in the Cursor dashboard.
(requestId: serverGenReqId_8b7aadcd-1175-4b7e-850c-562b38afc9d6)”

Expected Behavior

Bugbot runs again after increasing the usage limit

Screenshots / Screen Recordings

bugbot_not_running.png
bugbot_not_running.png1149×419 45.7 KB

Operating System

MacOS

Version Information

Not applicable

Does this stop you from using Cursor

No - Cursor works, but with this issue

7

Hi Oliver,

Thanks for the report and request ID. I confirmed that increasing the usage limit will not resolve this specific issue.

Bugbot is currently attempting to run through one of your team’s Unpaid Admin accounts. Unpaid Admins can manage team settings, but they do not have Cursor product usage. Since your team has paid members but no paid Admin, Bugbot is blocked and displays a misleading usage-limit message.

We’ve filed this as a bug internally. In the meantime, an Unpaid Admin can promote one of your existing paid Members to Admin here:

https://cursor.com/dashboard/members

Afterward, please run bugbot run again. Reconnecting GitLab should not be necessary. If it still fails, please share the new request ID and we’ll take a closer look!

8

Hi Kevin, this worked, thank you

9

Awesome thank you for confirming