my repo is stuck again- can't delete it by UI and API (how to resolve it)

[mend_automation_9]

Hi, 

I face the same issue again. I'm trying to delete repo by UI and by API request but without success.
in UI stuck with loading (without any details).
and by API I got:

requests.exceptions.HTTPError: Repository currently not available.

please need help - this issue affect my work
Could you please update the priority of the bug so it will get fixed faster?

[Theodora Boudale · Accepted solution]

Hi @mend_automation_9,

The Bitbucket account with the same email address as the community account that you used to make this post has access to one repo that is stuck in the 'Creating' mode. Please note that this is a different account than the one of the earlier community post you linked.

I went ahead and deleted this repo (since it has a size of 0 bytes, you are a workspace admin, and the repo cannot be deleted by end users).

If the issue concerns a repo in a different workspace, please leave a comment here after logging in to community with the email address of the Bitbucket account that has admin access to the repo's workspace, and I will look into it.

I have reached out to the development team regarding this bug https://jira.atlassian.com/browse/BCLOUD-22265, I will let you know when I have an update.

Kind regards,
Theodora

[mend_automation_9]

Thanks, The repo has been deleted.

[Theodora Boudale]

You are very welcome.

With regards to the bug https://jira.atlassian.com/browse/BCLOUD-22265, I'm afraid we don't have an ETA to share at the moment. The repo in question was created a long time ago, and we do not have any logs to check from that far back. If the issue occurs again, please leave a comment here as soon as the repo is stuck in 'Creating' so we check our logs and investigate further.

Kind regards,
Theodora

[Ohio]

Sorry you're facing this again. If both the UI and API fail with "Repository currently not available," the repo may be in a locked or corrupted state. 

I recommend contacting support with the repo name and error details, and asking them to escalate the issue. Mentioning that it's blocking your work should help prioritize it.