Forums

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

new repo stuck in creating repository state

Ben Martin-Peddey
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!
February 18, 2026

when opening link https://bitbucket.org/<workspace>/<repo>

the following is rendered:

Creating repository

Please wait a moment while we create your repository.

----

Context – how the repo was created
The repo was created via the Bitbucket Cloud REST API (API token auth), then we tried to use it from Git. Flow:
→ 403 (so we assumed it didn’t exist and tried to create it).
  1. POST https://api.bitbucket.org/2.0/repositories/<workspace>/<repo-slug>
Body: {"scm": "git", "is_private": true, "project": {"key": "<PROJECT_KEY>"}}
→ 201 Created (or 409 Conflict if it already existed from a previous attempt).
  1. Git (a few seconds later):
git ls-remote https://bitbucket.org/<workspace>/<repo-slug>.git
→ 403 with message: “This repository is currently not available.”
  1. The repdoes appear in the workspace repository list on the web, but opening
https://bitbucket.org/<workspace>/<repo-slug> or the repo’s admin/settings page shows only:
“Creating repository – Please wait a moment while we create your repository.”
It has stayed in that state for [X hours/days].
  1. DELETE https://api.bitbucket.org/2.0/repositories/<workspace>/<repo-slug>
→ Response body: “Repository currently not available.” (so we can’t delete it via API either).
So from our side: create via API succeeds (or we get 409), but the repo never leaves the “creating” state; Git and the DELETE API keep saying “repository is currently not available.” We’re using an API token with repository admin (and delete) scopes; the workspace and project otherwise work for other repos.
----
this is the only repo in the workspace that’s stuck

0 answers

Suggest an answer

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

Atlassian Community Events