Push blocked — "exceeded user limit" on brand-new Free workspace with only 1 user

[Automation]

Created a brand-new Bitbucket Cloud Free workspace (murua-media) today with a single member (a dedicated account). No prior paid plan, no downgrade, no failed payment, this is a fresh workspace.

Attempting git push (after creating the repo via the REST API) fails with:

remote: [ALERT] Your push failed because the account 'murua-media' has exceeded its
remote: [ALERT] user limit and this repository is restricted to read-only access.
fatal: unable to access '...': The requested URL returned error: 402

Only 1 user in the workspace, well under the 5-user Free limit. Same issue reported here with no resolution: https://community.atlassian.com/forums/Bitbucket-questions/Push-blocked-exceeded-user-limit-on-1-user-Free-workspace-4/qaq-p/3245121 (suspected orphan/duplicate Free-tier license records from unrelated past workspaces on the same account).

Is there a known backend propagation delay for new accounts/workspaces, or do I need to request manual cleanup of license records? Free plan doesn't qualify for a formal support ticket per your own docs, so posting here.

Update: Started working again on its own after a few hours, no changes made on my end (no plan change, no payment, no user removed). Seems to confirm this was a backend propagation delay for a new account/workspace rather than an actual limit or orphan license issue. Leaving this here in case it helps anyone else hitting the same false-positive.