Bitbucket repos removed earlier than expected - any way to restore?

[Yurik Mykhaletskyi]

Hi everyone,

I’m experiencing an issue with my Bitbucket repositories that were unexpectedly deleted.

I received notifications stating that inactive repositories would be deleted after May 15 if there was no activity. However, as of today (April 27), my repositories are already gone.

Has anyone else experienced early deletion like this?
Is this expected behavior or could it be an error?

Also, is there any way to restore repositories in this situation (especially on a free tier account)?

Any advice or similar experiences would be really helpful.

Thanks in advance!

[Ben · Accepted solution]

Hi @Yurik Mykhaletskyi 

I've gone ahead and re-activated your personal workspace. There are issues at the moment with the self-service recovery method, so support is handling these when needed.

Please check again and let me know how it goes :) 

Cheers!

- Ben (Bitbucket Cloud Support)

[Yurik Mykhaletskyi]

Hi Ben,

Thank you so much for the quick help! I can confirm that everything is restored and working perfectly now!

Really appreciate your support 🙌

Cheers,
Yurii

[Tomislav Tobijas]

Hey @Yurik Mykhaletskyi ,

You can check this article about the upcoming deactivation/deletion: Bitbucket cleanup of free unused workspaces: what you need to know 
Now, as stated in the docs, you should be able to restore your workspace by following the steps stated in the article. 

Also, I believe you should be able to raise a ticket on Atlassian Support to ask their team if they can reactivate the workspace and everything within it. 👀

Cheers,
Tobi

[Yurik Mykhaletskyi]

Hi @Tomislav Tobijas ,

Thanks a lot for your reply and the link!

Unfortunately, I’m unable to restore the workspace using the steps from the article. The "All workspaces" button is not clickable for me - nothing happens when I click on it.

Also, I tried to raise a support ticket, but it seems that creating tickets is only available for paid plans, so I don’t have that option.

Has anyone encountered a similar issue or knows any workaround in this case?

Thanks again for your help!