Bitbucket workspace stuck in read-only mode despite being within Free tier limits (ada_test_tool)

Question

My Bitbucket workspace ada_test_tool is locked to read-only, with pushes failing with:

[ALERT] Your push failed because the account 'ada_test_tool' has exceeded its
[ALERT] user limit and this repository is restricted to read-only access.

(HTTP 402)

I've verified this is not an actual limit issue:

* Total organization users: 1 (checked at admin.atlassian.com → Directory → Users)
* Bitbucket workspace users: 1 (checked via Workspace settings → User Directory, including the "all users on plan" filter — no hidden or unlicensed users)
* Workspace storage: 0 GB used (0%)
* Repository size: negligible — ada_test_tool/testing_tool contains only a README and a handful of small source files
* No pending invites, guests, or Trello/Jira/Confluence users contributing to any shared collaborator count

Atlassian's own support bot confirmed this looks like a stuck backend flag or synchronization issue, but stated it lacks permission to clear it and that Free-plan workspaces don't have access to a direct technical support ticket. Posting here per that guidance.

Could an Atlassian staff member help clear this restriction on workspace ada_test_tool? Happy to provide any additional account details needed.

Arkadiusz Wroblewski · Accepted Answer

Hello @Vinothraj Muneeswaran

Please also check that:

https://support.atlassian.com/bitbucket-cloud/kb/bitbucket-cloud-removing-users-from-project-or-repository-settings-still-shows-under-users-on-plan/

https://support.atlassian.com/bitbucket-cloud/kb/fix-error-your-push-failed-because-the-account-has-exceeded-its-user-limit/

Best

Arek 🤠

Ben · Accepted Answer

Hi @Vinothraj Muneeswaran

I have verified that your workspace does not exceed the user limit, so this is a false positive.

I can see that the workspace was created 20 hours ago. There is a known issue with our new billing platform which causes this error message if GIT actions are attempted shortly after creation, as there is an initial delay in sync between the workspace itself and the billing platform for a short period of time.

The current guidance is to simply wait, as this resolves itself automatically once the sync is complete. Our internal tooling shows that this restriction is no longer present against your workspace - so this should be functioning as normal.

Please let us know if you are still encountering issues.

Cheers!

- Ben (Bitbucket Cloud Support)