Hello Atlassian Team,
I am unable to enable Bitbucket Pipelines in my existing workspace.
When I turn on "Enable Pipelines" under Repository settings → Pipelines → Settings, the switch briefly appears enabled, but reverts to OFF after refreshing the page.
The request fails with the following error:
404 Not Found
account-service.account.not-found
Account {7ab53943-c8d2-4a91-92b9-7b88a7449f4c} does not exist.
However, the Bitbucket Workspace API successfully returns the same UUID:
- Workspace slug:
rohphillip - Workspace UUID:
{7ab53943-c8d2-4a91-92b9-7b88a7449f4c} - Repository:
GeoQuiz - Branch:
feature/redesign bitbucket-pipelines.yml is already committed and pushed.
Git operations and repository access work normally. Only Pipelines activation is failing.
This appears similar to BCLOUD-21974, although I have not established whether repository transfer is involved.
Could you investigate whether the Pipelines backend has a missing or stale workspace account association and help restore the ability to enable Pipelines?
Thank you.