[validation_error] Failed to verify existence of branch

Support Bug Reports
, ,
1

Where does the bug appear (feature/product)?

Cursor SDK

Describe the Bug

The issue described in this task has returned: [validation_error] Failed to verify branch 'Dev' on Bitbucket Cloud — integrations shows Connected, Taskmaster/API token can list branches

Same exact reproduction steps or behavior. No Cloud Agents can be started using the SDK on Bitbucket at least since that’s what I use.
It has been broken since 24 September at least.

Steps to Reproduce

Try to start a cloud agent through the SDK with a Bitbucket repo.

Operating System

Linux

Version Information

It’s the SDK.

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

5

Hey, thanks for the report. This looks different from the thread you linked. That issue 170395 was fixed in early September and had a different cause.

Here it looks like the Bitbucket auth saved on your account stopped being accepted during token refresh. Because of that, any branch check fails and you get a misleading message about the branch name. At the same time, in Integrations it may still show as Connected.

Try reconnecting Bitbucket:

  1. Open cursor.com/dashboard, go to Integrations.
  2. Next to Bitbucket, click Disconnect.
  3. Click Connect again and approve access in Bitbucket using the account that can see your repos.
  4. Re-run your SDK script on the same repo and branch.

If it still fails after that, send the attempt time with timezone and the exact repo and branch, and I’ll take a closer look.

6

You are right, thank you for noticing this, sorry about rushing with the report.