Hi Bitbucket Cloud team,
I can't enable Pipelines on a private repository in my Free workspace "javier_lazaro". The contact form sends Free workspaces to the Community, so could an Atlassian staff member please raise an internal ticket for this? I can share the full identifiers privately.
What happens:
In Repository settings > Pipelines > Settings, the "Enable Pipelines" switch turns on, but after a page reload it is off again. The repository has 0 builds, so bitbucket-pipelines.yml is never reached.
Error:
On 2026-10-09 the PUT that the web UI sends to .../repositories/javier_lazaro/<repo>/pipelines_config returned HTTP 404. On 2026-11-12 an authenticated GET to the same pipelines_config endpoint returned the same error, while the repository metadata endpoint works:
key: account-service.repository.not-found
message: Repository {298a234a-...} does not exist for account {a8148f8e-...}.
What we found:
- The account in the error, {a8148f8e-...}, is the UUID of workspace "javier_lazaro" (a legacy personal workspace).
- The repository API reports the owner as "javier_lazaro-team", with a different UUID, {88379875-...}, which is not visible as a workspace.
It looks like the repository still belongs to a legacy team account, so the Pipelines account service can't find it under the workspace account.
Request:
Could you fix the internal association so that the repository owner matches the workspace, without transferring, renaming or recreating the repository? If that isn't possible in place, please tell me the supported procedure and what it would change.
Please don't enable Pipelines or start a build for me. I'll do that myself once you confirm the fix.
Timezone: Europe/Madrid (CET).
Thanks!