Hello everyone. Thanks for your patience, and I apologize for not responding sooner. The good news is that we are actively working on a solution for this issue right now.
To give you an idea of what's happening: when new changes are pushed to a repository on Bitbucket, we queue up a background task to update ahead/behind for your branches. We've had intermittent issues with that queue, which is shared by all customers, becoming backed up. That problem has worsened recently.
We're taking a multi-pronged approach to solving this.
First, we are limiting the influx of new background tasks from a very small subset of users who are abusing our platform with an excessive volume of automated pushes.
Secondly, we are working to improve the efficiency of our ahead/behind algorithm so that we can process the queue more quickly.
We expect to have the issue resolved within the next couple of weeks. I will post updates here.
In the mean time, you can work around this by calculating these numbers locally using git. I recognize that this is not nearly as convenient as the broken functionality on Bitbucket, but it should help if you really need this information in a pinch.
Thanks again for your patience while we work on this problem.
Hey Community! We’re willing to wager that quite a few of you not only use Bitbucket, but administer it too. Our team is excited to share that we’ll be releasing improvements throughout this month of...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events