Issue Summary

When adding a file (first commit) to a newly-created empty repository through the Bitbucket Cloud REST API, the request intermittently fails with HTTP 404 Repository Not Found, even though the repository exists and is accessible. The error appears at random and only during the initial commit cycle. This bug appears to only be affected for UUM workspace

Steps to Reproduce

1. In a loop, Create empty repository (via REST API) and call POST /2.0/repositories/{workspace}/{repo_slug}/src (or equivalent) to add a file and commit.
2. Log the HTTP status code for each request.

Expected Results

All the requests including commit request returns HTTP 201 Created and the file is added successfully.

Actual Results

Some commit requests attempts return HTTP 404 Not Found with the message “Repository not found”.

Workaround

Add a retry mechanism with a ~5-second back-off. In most cases, the commit succeeds within 1–2 retries.
If the error persists after retries, please escalate to Atlassian Support.