Cannot enable Pipelines: existing workspace UUID returns account-service.account.not-found

AriannaMiao

I cannot enable Pipelines for AriannaMiao/qcp_online_verifier. After clicking “Enable Pipelines”, the controls remain disabled. Refreshing shows Pipelines is still disabled. The issue also occurs in an incognito window.

The failing request is:

It returns HTTP 404:
Account {73784eea-2de1-4fad-bb09-ac4a88412ba3} does not exist.
Error key: account-service.account.not-found

However, querying /2.0/workspaces/AriannaMiao succeeds and returns:
uuid: {73784eea-2de1-4fad-bb09-ac4a88412ba3}
name: AriannaXuan
slug: AriannaMiao

As far as I know, the repository has not been transferred.

Could you investigate why Pipelines cannot resolve this existing workspace UUID and help restore the ability to enable Pipelines?

Anwesha Pan

Hi @AriannaMiao👋🏻

First of all, welcome to community! ✨

The error HTTP 404: Account {73784eea-2de1-4fad-bb09-ac4a88412ba3} does not exist (account-service.account.not-found) occurs due to an internal microservice desynchronization between Bitbucket's core Workspace registry and the Bitbucket Pipelines backend provisioning service.

You could try the below troubleshooting steps:

1.Direct Commit of bitbucket-pipelines.yml

Sometimes the UI toggle endpoint fails, but committing a configuration file triggers the internal provisioning hook automatically:

1. In your local repository qcp_online_verifier, create a basic bitbucket-pipelines.yml:

image: atlassian/default-image:latest


pipelines:

  default:

    - step:

        name: Test Pipeline Initialization

        script:

          - echo "Pipelines provisioned successfully"

2. Commit and push this file to the default branch (main or master):

git add bitbucket-pipelines.yml

git commit -m "Initialize Bitbucket Pipelines"

git push origin <default-branch>

3. Navigate to Repository Settings -> Pipelines -> Settings or the Pipelines tab to check if the pipeline executed or registered.

2. Verify Workspace-Level Permissions & Billing Profile

1. Navigate to Workspace Settings (https://bitbucket.org/AriannaMiao/workspace/settings/).
2. Verify that your user account is listed under User groups > Administrators with full Admin permissions.
3. Check Plan details or Billing to ensure the workspace is fully linked to an active Atlassian Cloud ID/subscription profile.

If this doesn't work, please feel free to submit a ticket - https://support.atlassian.com/contact/

I hope this helps & resolves your issue. 🙂

Thanks,
Anwesha