Where does the bug appear (feature/product)?
Bugbot / Security Review Agent
Describe the Bug
On Bitbucket Cloud, adding a repository to Rollouts fails whenever Cursor already has a webhook saved for that repo. Our two main repos can’t be added. Unused repos save fine the first time, but any later save that includes them fails too.
Rollouts seems to update the Cursor webhook it has saved for the repo instead of creating a new one. Bitbucket rejects the update with “Method not allowed”. If that webhook has been deleted in Bitbucket, the save fails with " is not a valid hook", and no new webhook is created.
Errors seen in the repo picker:
Failed to update rollouts team settings: 400 {“error”:{“message”:“{"type": "error", "error": {"message": "Method not allowed"}}”, … “ERROR_BAD_REQUEST” … “isExpected”:true}]}
Failed to update rollouts team settings: 400 {“error”:{“message”:“{"type": "error", "error": {"message": " is not a valid hook"}}”, … “ERROR_BAD_REQUEST” … “isExpected”:true}]}
Steps to Reproduce
Use a Bitbucket Cloud workspace with the Cursor app connected. Use a repo that has never been added to Rollouts and has no Cursor webhook.
Go to Automations → Rollouts → Code access → Add repository, select that repo, and click Save. It succeeds, and a “Cursor Bugbot” webhook appears on the repo in Bitbucket.
Save again with that repo still selected, for example after adding another repo. It fails with “Method not allowed”.
For a repo that already had a “Cursor Bugbot” webhook from an earlier Bugbot setup, the very first Rollouts save fails with “Method not allowed”.
Delete that repo’s Cursor webhook in Bitbucket (Repository settings → Webhooks) and save in Rollouts again. It fails with " is not a valid hook", and no new webhook is created.
Expected Behavior
Saving Bitbucket Cloud repos in Rollouts should work whether or not a Cursor webhook already exists on the repo. If the saved webhook is missing, Rollouts should create a new one.
Screenshots / Screen Recordings
Operating System
MacOS
Version Information
Cursor Dashboard (web), Automations → Rollouts
Additional Information
Every repo that failed had a “Cursor Bugbot” webhook created by our original Bugbot setup in August. Every repo that worked had no Cursor webhook until Rollouts created one.
Turning Bugbot off and on for the repo, and using Bugbot “Enable All”, didn’t recreate the deleted webhook or clear the error.
Bugbot itself still works on the repo with no webhook at all. A bugbot run comment started a review straight away. So the old per-repo webhooks look like legacy, and the bug is only in the Rollouts save.
Could you clear the saved webhook IDs for our two main repos so we can add them to Rollouts? I can share the team, workspace, repo names and hook IDs privately.
Does this stop you from using Cursor
No - Cursor works, but with this issue