Workspace: dcuconati (display name: Daniel C…)
Repository: dcuconati/evc-promo-builder (private, Free plan)
Problem
The "Enable Pipelines" toggle under Repository settings → Pipelines →
Settings is disabled/greyed. Clicking it does nothing and it resets after
refresh. The UI's own calls return 404:
PUT https://bitbucket.org/!api/2.0/repositories/dcuconati/evc-promo-builder/pipelines_config
-> 404 Not Found
GET https://bitbucket.org/!api/internal/workspaces/dcuconati/pipelines-config/allowance
-> 404 Not Found
HEAD https://bitbucket.org/!api/internal/accounts/{680e34f9-UUID}/pipelines_config
-> 404 Not Found
POST https://api.bitbucket.org/internal/site/addons/account/{680e34f9-UUID}/install/
-> 404 Not Found
API attempt
Created a scoped API token with admin:repository:bitbucket and
write:pipeline:bitbucket, then:
PUT https://api.bitbucket.org/2.0/repositories/dcuconati/evc-promo-builder/pipelines_config
Body: {"enabled": true}
Response:
{"error":{"message":"Not found","detail":"Account {800c5d3f-UUID}
does not exist.","data":{"key":"account-service.account.not-found",
"arguments":{"uuid":"{800c5d3f-UUID}"}}}}
Note: the account UUID in the token error (800c5d3f-…) differs from the
UUID in the browser session (680e34f9-…). I suspect the workspace and the
Atlassian identity used for API tokens are not the same account, or a
Google-SSO-linked account is mis-mapped.
Already tried
- Email verified; two-step verification enabled; connected/installed apps cleared.
- Incognito window and a second browser; hard refresh.
- Re-authenticated with "Log in with Google".
- API token via Bearer and Basic (email as username); same account error.
Questions
- Is Bitbucket Pipelines provisioned for my workspace?
- Which Atlassian account owns the workspace, and why do the two UUIDs differ?
- Can the account/add-on provisioning be repaired (or the identities
reconciled) so Pipelines can be enabled?
