Workspace rename stuck 48+ hours after recent account username change (Slug unavailable / 404)

[Shimon Rothschild]

I initiated a workspace rename from <OLD_WORKSPACE_SLUG> to <NEW_WORKSPACE_SLUG> about two days ago. The rename has not completed, and I'm seeing inconsistent behavior across the UI and API:

• Current status: The workspace still displays the old slug everywhere (browser URLs, API responses, clone URLs).

• Retry attempt: Attempting the rename again reports the target slug (<NEW_WORKSPACE_SLUG>) as "not available".

• Direct URL: Navigating directly to bitbucket.org/<NEW_WORKSPACE_SLUG>/ yields a 404 error.

• Workspace Switcher: The new workspace slug does not appear in my workspace switcher.

• UI Pickers: However, <NEW_WORKSPACE_SLUG> does show up as a selectable option in certain UI dropdown pickers (e.g., when selecting a workspace context while creating a community post). It seems to exist at some internal database level, but isn't accessible or usable anywhere.

Additional Context: Shortly before initiating this workspace rename, I changed my personal account username from <NEW_WORKSPACE_SLUG> to a new name to free up that specific handle for the workspace.

It seems possible that changing the personal handle left a stale reservation or orphaned record tied to the original account handle that is now blocking the workspace rename job from finalizing.

Since this has been stuck for 48+ hours, is this a known backend job deadlock, and can an Atlassian admin help clear the reservation lock?

(Note: Happy to provide original workspace IDs and actual usernames privately to support staff if needed.)

[Ben]

Hi @Shimon Rothschild 

This is an issue with legacy personal workspaces (which you have), as username is closely associated with workspaceID.

I've changed this in the backend, your username matches your workspaceID now - can you check this for me and let me know if that's the expected change?

If not - please change your workspaceID to the correct ID (I'll see this on my end) and let me know if you'd like your username to match it, no need to share anything here:

• https://support.atlassian.com/bitbucket-cloud/docs/change-a-workspace-id/

Cheers!

- Ben (Bitbucket Cloud Support)

[Shimon Rothschild]

No, not resolved. 

1. Old name still listed and works.

2. I tried to change it to the new name get the same message : This workspace ID is not available.

3. I tried navigating to the proposed new name; it returned a 404 Not Found.

What should I do instead?

[Ben]

Hi @Shimon Rothschild 

May you please share your timezone so I can raise a support ticket on your behalf with the team that operates during your working hours?

This won't be able to be resolved in community, as it would involve sharing your intended workspace ID.

Cheers!

- Ben (Bitbucket Cloud Support)

[Shimon Rothschild]

Agreed, my timezone is GMT + 2. Thank you.

[Ben]

Hi @Shimon Rothschild 

I've raised a ticket on your behalf, you will receive a response shortly during your timezone :)

Cheers!

- Ben (Bitbucket Cloud Support)

[Shimon Rothschild]

Thank you. Forcing public forum posts to reach tech support compromises user privacy and is poor customer service. Other organizations handle this better by allowing private ticket submissions, with an option to pay if community assistance could be a viable solution. Please consider this policy.