Cannot enable Pipelines: account-service.account.not-found, including a newly created repository

bazusaladra

Hello Atlassian team,

I cannot enable Bitbucket Pipelines for private repositories in my Bitbucket Cloud Free workspace. The support form directs Free-plan technical issues to Community.

Steps to reproduce:

1. Open Repository settings > Pipelines > Settings.
2. Turn on Enable Pipelines.
3. The switch becomes checked and disabled while saving.
4. Reload: the switch returns to off, and Pipelines remains unavailable.

The enablement response from the original repository contains:
message: Not found
detail: Account {account UUID redacted} does not exist.
data.key: account-service.account.not-found

On 27 October 2026, I also created a new private repository in the same workspace and project, without transferring the original repository. I tried enablement both while the new repository was empty and after pushing the code and a valid bitbucket-pipelines.yml to main. Both attempts produced the same checked/disabled switch and reverted to off after refresh. I have not captured a fresh account-service response for the new repository, so only the UI symptom is confirmed there.

The corrected pipeline YAML passes validation against the official schema at https://api.bitbucket.org/schemas/pipelines-configuration. Repository creation and Git pushes succeed, and the local build/test/acceptance checks pass. Hosted CI is blocked because enablement cannot be saved.

I found BCLOUD-21974 (https://jira.atlassian.com/browse/BCLOUD-21974), which documents the same error after repository transfer. I have not established that this is the same cause; the original repository's transfer history has not been confirmed, and the newly created repository also fails.

Could Atlassian investigate whether Pipelines provisioning or account/workspace associations are missing or stale, and advise how to restore enablement? I can provide the workspace, private repository URLs, and the exact account UUID through an appropriate private support channel.

Thank you.

Trevan Householder_Isos-Tech-Consulting_

@bazusaladra , thanks for the clean repro. Testing a brand-new repo was smart, because it rules out the repo and points at the workspace. You're not alone, either. This thread…

https://community.atlassian.com/forums/discussion/3310318/cant-enable-pipelines-account-54c6f884-c96c-4f13-a63f-aae6233c2e4d-does-not-exist

and a few other recent ones on Free workspaces show the same 404 with no transfer involved. In one, the UUID in the error matched the workspace UUID. That suggests the Pipelines backend has no record of the workspace, which nothing on your side can fix.
One cheap thing to try first is the workaround from BCLOUD-21974.

https://jira.atlassian.com/browse/BCLOUD-21974

Invite a second user, make them admin on the repo, and have them enable Pipelines. It's documented for transfers, so it may not take here.
If it doesn't, I'd comment on and vote for that bug with your error. It sits in "Gathering Impact", so reports help. Does the UUID match your workspace's?