Possible Throttling issue when we are using Bit Bucket with Azure DevOps

[Mukul Sharma]

Hi Team,

We are using Bit Bucket with our CI/CD tool Azure DevOps but we have noticed that random information builds are getting generated which as per Microsoft could be because of throttling on Bit Bucket repo.

Have the below queries if you can assist :-

1. Can I validate that throttling is being experienced by our Bit bucket which is causing this random information builds getting triggered?

2. Have such issues being raised by other customers as well and what were the possible solutions suggested to them ?

Please find below the error that we are receiving as per information build.

"

• Could not retrieve file content for {file_path} from repository {repo_name} hosted on {host} using commit {commit_sha}.

"

Also Microsoft response for this issue has been below "Since all your source code are from bitbucket repo, it’s suggested to contact BitBucket to understand why they are being throttled.". Kindly suggest.

[Patrik S]

Hello @Mukul Sharma and welcome to the Community!

Bitbucket Cloud indeed implements varying rate limits on the public APIs in order to grant the stability of the platform for all users. 

For authenticated API calls, the rate limits are implemented at the user level, where a user being rate-limited will temporarily receive an HTTP 429 status code when making API requests.

If you find that a particular user is constantly being rate-limited, one option would be to spread the workload across multiple users/resources or identify if the existing workload is unexpected/unnecessary. You can find this information and other possible mitigation steps in our rate limit troubleshooting guide.

That being said, checking our internal logs for the bitbucket workspace you have access to, I don't see any occurrence of rate-limiting in the last 7 days, so the issue you are facing may not be directly caused by rate-limiting/throttling. 

In this case, for testing porpoises, I would suggest the next time the issue occurs on the Azure environment, try to clone the same repository locally with the same credentials and check if the error is also reproducible outside of Azure. This can help to isolate if the issue is related to some Azure environment, or with the repository itself.

Hope that helps! Should you have any questions, feel free to ask.

Thank you, @Mukul Sharma !

Patrik S