Noe
(Noé)
April 14, 2026, 2:38pm
1
Where does the bug appear (feature/product)?
Somewhere else…
Describe the Bug
I’m attempting to connect our Gitlab account and keep getting a “high volume and rate limits” error message.
Steps to Reproduce
Expected Behavior
connect successfully to gitlab
Screenshots / Screen Recordings
Operating System
MacOS
Version Information
I’m on the cursor website
Does this stop you from using Cursor
Yes - Cursor is unusable
Having the same issue. Sometimes after multiple refreshes it’ll show me as connected and my gitlab username is there, but when I refresh again or try an automation, I disconnect again.
jade.x
April 14, 2026, 3:22pm
7
can we also check if this is impacting Bugbot? our automatic reviews in Gitlab have stopped as of yesterday, and I encountered this same issue trying to connect another gitlab account in our admin panel.
we’re on an enterprise plan
Colin
(Colin)
April 14, 2026, 3:28pm
8
Hey all,
Thanks for the reports. We’ve seen some other reports this week (and especially today) of connectivity issues with Gitlab. We’ve raised this to our developers.
For us, Bugbot is not working anymore
What I also noticed:
gitlab is disabling the webhook due to slow replies from cursor
there are not over 500+ cursor bots added to my gitlab project
I’ve disabled the integration, but is annoying since we started relying on bugbot for reviews.
Colin
(Colin)
April 15, 2026, 11:00am
11
Hey there.
The GitLab issues reported yesterday should be resolved fixed!
@Mathias_Colpaert I would suggest reenabling the Webhook and trying Bugbot again. If it still fails, please raise a new thread.
@Colin How can I clean up this long list of cursor bots on my project? These are managed by Cursor right?
Colin
(Colin)
April 16, 2026, 3:43pm
13
@Mathias_Colpaert Unfortunately, according to GitLab’s docs , they cannot be cleaned up manually.
They are members of the project, but cannot be removed from the project or added directly to any other groups or projects.
If you revoke the Project Access Token related to those bot users (or it otherwise expires), the bot user is retained for 30 days.
@Colin I’m having the same issue with a Gitlab Self Hosted instance. Should I open a new ticket or can we use this one?
Seems like an intermittent issue, as trying a third time worked