Something went wrong. Try again by commenting “Cursor review” or “bugbot run”, or contact support (requestId: serverGenReqId_78308f7b-6dd5-4f57-b0fb-2b58fa56b641).
Steps to Reproduce
Comment “bugbot run” or “@cursor review” on a PR in BitBucket.
Bugbot did start on that Bitbucket PR, but the review failed before it finished - the requestId in the error is noted. Bitbucket is still in public beta.
Have a Bitbucket workspace admin and a Cursor team owner confirm the full setup from the Bitbucket docs:
Cursor app installed on the workspace, then Connect to Cursor linked to your Cursor team
Your account Connected to Bitbucket under Integrations
Then on the PR, comment cursor review verbose=true (or bugbot run) and share the PR URL plus the new requestId if it fails again. The mangled heading is a separate formatting issue in those error comments - it doesn’t change that the run failed.
Your account Connected to Bitbucket under Integrations
Commented bugbot run verbose=true on the PR again (~1hr ago).
There has been no comment from the Cursor. We are also not seeing any status as described in the docs Bugbot | Cursor Docs
Something went wrong. Try again by commenting “Cursor review” or “bugbot run”, or contact support (requestId: serverGenReqId_344b14c2-0510-4893-9391-c45f7ac2caa8).
Something went wrong. Try again by commenting "Cursor review" or "bugbot run", or contact support (requestId: serverGenReqId_7124d558-704c-448b-aac6-6d5bc15f639a).
Thanks for confirming the setup - that rules it out, and BugBot being able to post comments means the connection is working. So there’s nothing more to change on your end.
I dug into the request IDs you shared, and this is a bug on our side, not your configuration. BugBot’s review is failing at the step where it fetches the PR’s changes, specifically on Bitbucket Cloud PRs that come from a forked or separate repository. It’s a known issue with the Bitbucket Cloud integration (still in public beta) and we’re working on a fix.
In the meantime, if the same change can go through a PR whose source branch lives in the same repository (rather than a fork), BugBot should be able to review it. If PR #703 is coming from a fork, that confirms you’re hitting exactly this case.
The PR is not from a fork — the source branch @devs_name/cursor_bitbucket_test lives in the same repository (company_name/project_name) as the destination master. Note the branch name contains an @ prefix, and the PR is currently a draft, in case either is relevant to the fetch failure.
