Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Ahead / Behind works randomly 'Commit activity unavailable...' ?


hy?  seems random grrreeat :slightly_smiling_face: but only when I really want to see ahead/behind


btw - it works if I don't need the info



14 answers

1 accepted

4 votes
Answer accepted
Kavi Laud Atlassian Team Jun 03, 2020

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 thanks for the reply and the detailed informations :)

Is this problem already solved? I just got this error o_O

We're having the same problem

Having the same problem here, and cannot create new release branches.. Created a ticket for it.

Would you mind linking to that ticket?

Same problem also for us from many days

got the same issueBildschirmfoto 2019-08-20 um 16.49.02.png

Happening to us too

us as well yesterday but started working again after an hour or so. never indicated anything amiss during that time.

Any fixes? Like 75% of the time we're having this issue

Is there any fix coming for this issue?


Also, I don't know if it's related but I have this error in my console



Same here

Same problem here 

Same here. It happens every once in a while. This time the whole day.

Same prob here :-(

Having the same problem

Having the same problem

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events