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

How to prevent Sourcetree from switching back to Generic Account on optional extended integration.

I'm having a problem regarding a red exclamation point on the Remote Icon on the upper right part of Sourcetree, it the prevents push/pull functions.

The usual remedy for this is to stop using the generic account and choose my actual remote account instead. 

But the problem is that Sourcetree reverts to using the generic account after a few hours or so, causing me to do the fix again.

I'd like to find a way to resolve this issue.

Using version

13 answers

it's insane the amount of annoying bugs they are introducing at every version, it's really bad right now a pain to use this.

Same problem exists in 3.3.8. Is Atlassian going to fix this bug?

Still happening today on 3.3.8. Really slows us down, this needs to be fixed asap.

Same problem.

Using version


Co-Worker uses 3.2.6 -> no Problem

the best idea is to downgrade the app :\

Like Daniel S. likes this

Resolved by uninstall and install 3.2.6

This worked for me

Like # people like this

I finally downgraded back to 3.2.6 again.  Thanks for the tip.

Like Rodrigo Hernangómez likes this

Upgraded today from version 3.3.4 to version 3.3.8 (on Windows 10), the issue is still present.

Also the internal update checker (Tools > Options > Updates > Check For Updates) was not showing that there is a new version 3.3.8 available. Found the new version by visiting the Sourcetree website.

Same problem.

Using version 3.3.4.

As several persons have already suggested in this post I uninstalled Sourcetree 3.3.8 and installed 3.2.6 instead. Using Windows, don't know about other OS's.

Now I don't have that problem any longer.

Hopefully the people at SourceTree will fix this issue so I can upgrade to a current version again.

Yes, this is really annoying.

Setting the default account in the "Tools > Options > Authentication" doesn't help.

This appears to be fixed with version 3.4.3 (3.4.4 is out as of this post).

From Release Notes:

  • Fixed Optional integration settings not being saved


Did you try this with 3.4.3?

Looking at the release notes I don't see it mentioned anywhere unless this is part of "Fixed Optional integration settings not being saved".

The fix "Fixed Launch ssh agent option in Tools not doing any operation" does not apply since my Pageant (SSH Agent) is launched all the time

Just want to know before I upgrade since I don't want to have to downgrade again. :)

Did Windows ver. 3.3.9 fix this issue?

I also found the following steps useful in removing the dreaded Remote Exclamation Mark.

  1. Ensure to un-stage files to apply fix.

  2. Delete all git, hg and sourcetree credentials in Windows > Credential Manager.

  3. In SourceTree go to Tools > Options > Authentication and reauthorise your token with Bitbucket.

  4. In Sourcetree, for each repository click in the toolbar:

    • Repository > Click the origin path > Click >Change Account from Generic to your Atlassian Account // In the question description but just being consistent :)

Spent half an hour doing this and it didn't work for me. I was really hopeful, as this is one of the most irritating faults with this product.

Being new to Sourcetree, my first thought was,, that I made a mistake in the configuration. Sort of happy now to see, that it wasn't me but Sourcetree. I would even be happier when this gets fixed of course.

I've been fortunate to start using SourceTree for the first time on MacOS.
It worked pretty good: however the Windows-versions seem to be bug-infested, mediocre and unstable! Luckily there are better alternatives for Windows-OS (e.g. GitExtensions)
IMHO it seems that Atlassian is giving less attention to making a good Windows-tool and they really should be ashamed of wasting developer time with such an amateuristic tool.

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events