You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Hey,
So I have this error message Bitbucket Api limit exceeded, and found the article below:
https://support.atlassian.com/bitbucket-cloud/docs/api-request-limits/#How-calls-are-measured. It is good article that explain how the request limit calculated, and I need to know how did I reached the limit.
In the past the developer waited to the next day and it resolved itself, but I would like to know what caused us reaching the limit, how can I get information about the activity that happened specially when you big team working on big project:
Activity / number of calls/ users/ pipeline.... stats or audit summary, abnormal activity?
As far as I know, you do not have that insight what and how caused exceeding the limit.
If I were you, I'd track down the problem on the client side (i.e. your side!) by adding extensive logging around the Bitbucket API calls. It would help you identifying how and when generates excessive load, which would be the input to optimize it (== reduce or defer the API calls if possible).
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.