Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Workspace ID “lchzh3473” shows “taken” but URL returns “Resource not found”

lchzh3473
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
December 22, 2025

Hello,

I am unable to use the Workspace ID “lchzh3473” in Bitbucket Cloud.

When I attempt to create or rename my workspace to this ID, the system shows the error:
“This workspace ID is already taken. Try another ID.”

However, visiting https://bitbucket.org/lchzh3473/
returns “Resource not found”, which suggests that no active or publicly accessible workspace exists under this ID. This appears inconsistent with the validation error.

I would like to understand the backend status of this Workspace ID:

Is it reserved, locked, or associated with a deleted or inactive workspace?

Is this expected behavior?

If no active workspace exists, is there any supported way to release or reuse this ID?

Current Workspace ID: lchzh3473-1 (temporary)
Steps taken: Workspace settings → Change Workspace ID → Enter lchzh3473

Thank you for any guidance.

2 answers

0 votes
Ben
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
December 25, 2025

Hi @lchzh3473 

That is an active user account (associated with your user email). You can no longer create workspaces with the same ID as a user account, all user accounts & their associated workspaceID's must be kept unique.

You will need to pick a different ID when creating a workspace, or change your username to free it up for usage by your workspace: https://support.atlassian.com/bitbucket-cloud/docs/update-your-username/

Cheers!

- Ben (Bitbucket Cloud Support)

0 votes
Aron Gombas _Midori_
Community Champion
December 23, 2025

I think Confluence and/or Jira has a similar behavior with space keys. When you delete a space, its key will not be "released" for a while.  It takes time (or maybe even an explicit "empty the trash") until the key can be taken again for a new space.

Which means that you should try it again later or open a ticket for Atlassian to empty the "workspace key trash".

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
TAGS
AUG Leaders

Atlassian Community Events