Bugbot stalled on Bitbucket, and GitLab automations won't start
Staff say both broke on Cursor's side on Oct 21. Don't reinstall anything; here's how to get reviews in the meantime.
If Bugbot stopped reviewing your Bitbucket pull requests, or your GitLab-triggered Cursor automations went quiet, it isn't your setup, so don't reinstall anything. Cursor staff confirmed both on the forum this morning as problems on Cursor's side that started Oct 21. Neither has a fix time yet.
- Who: Bitbucket Cloud workspaces using Bugbot, and anyone with a Cursor automation triggered by GitLab events.
- Symptom: no Bugbot review on new pushes or bugbot run comments in Bitbucket; GitLab events get an HTTP 200 but no automation run.
- Status: known issues, tracked by the team, not fixed.
What changed#
Bitbucket and Bugbot. Cursor staff member Colin wrote at 9:12 AM ET: "Since late on Oct 21 (UTC), Bitbucket Cloud pull request events from the Cursor app are reaching us but are not being passed on to Bugbot, so neither automatic reviews nor bugbot run comments start a review." In the same reply: "It affects Bitbucket Cloud workspaces broadly, not just yours." The poster said "We haven’t had a successful run since Oct 21, 06:49 PM (UTC)" (2:49 PM ET) and had already deleted and reinstalled the Bitbucket app.
That came after the Oct 21 Bitbucket incident on Cursor's status page, which closed at 1:53 PM ET and which we listed as resolved. The status page still read "All Systems Operational" at 10:30 AM ET today, so it isn't a reliable signal for this one.
GitLab automations. In a separate thread at 10:08 AM ET, Colin said the GitLab event "reaches us and matches your automation’s trigger, but the run then fails to start because of a server-side issue on our end. It began on October 21 and affects automations triggered by GitLab events." He added: "Bugbot and dashboard test runs take a different path, which is why those still work."
Why it matters#
Both fail quietly. A pull request can look like it passed review when Bugbot never saw it, and a GitLab automation returns success to GitLab without doing any work. Until the fix, assume a missing review means no review happened.
What to do now#
- Don't reinstall or reconnect. For Bitbucket, Colin says "there’s no need to reinstall the app or reconnect accounts again." For GitLab, he says: "You don’t need to change your automation, its trigger or its comment filter, and there’s no need to recreate it again."
- GitLab: "start the automation manually from its page in the dashboard (the same way you ran the test) when you need a review on a merge request," per Colin.
- Bitbucket, after the fix: "For any PR opened or updated in the meantime that still has no review, commenting bugbot run on it should start one," Colin wrote.
If a Bitbucket review can't wait, the poster reports that "calling /review-bugbot within cursor still fires." That's one user's report, not a staff workaround.
Good to know#
- Both started Oct 21, but staff describe them in separate threads and haven't linked them.
- Bugbot on GitLab still works, per Colin. Only GitLab-triggered automations are stuck.
- Our read: keep a list of Bitbucket PRs that got no review this week, so you can comment bugbot run on the open ones once it's fixed.
What to watch#
For Bitbucket, Colin said "I’ll update this thread when it’s resolved." The GitLab reply says "We’ll update this thread once GitLab-triggered runs are working again." We'll update this entry when staff say either is fixed.
