I am experiencing a persistent "read-only" lock on a newly created workspace (zevsas). Despite being the only user and having no significant data stored, all git pushes fail with: "Your push failed because the account 'zevsas' has exceeded its user limit."
Technical Details for Support:
Workspace ID: zevsas
Plan: Free
Current User Count: 1 (Verified in Workspace settings > User directory) 1
Storage Usage: 0% of 1GB (Verified in Plan details)
Symptoms:
Git push fails with user limit alert.
Original workspace (oomang) returns 404/Resource Not Found despite being the admin.
API attempts return "Token is invalid or not supported."
Troubleshooting Performed:
Confirmed no pending invitations or "ghost" users in the directory.
Verified no billing issues or overdue payments (never had a paid plan on this ID).
Confirmed repository size is well under the 4GB hard limit.
It appears to be a backend synchronization issue where the "read-only" flag is stuck. Could a Community Leader or Staff member please escalate this to have the workspace status refreshed?
This really looks like a backend sync issue, not something wrong with your setup. You already checked the user count, storage, invites, and billing, so the “user limit exceeded” error is probably coming from a stuck workspace flag. The 404 on the old workspace and invalid API tokens make it seem like the account metadata is out of sync internally. A staff member will likely need to manually refresh the workspace status on the backend.
Hello @oomang
I’ve requested assistance for you. An Atlassian Support Engineer will review the post and respond in this thread within 2 business days.
Best,
Arkadiusz
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.