Hello,
Two weeks ago, while using Sourcetree, I became aware of the CHANGE-3222.
It took me awhile to get my API token setup and working correctly but I was eventually successful and have been able to use sourcetree.
Then yesterday I was again confrunted with the inability to access bitbucket, I checked and this was during a Brownout Window. I have repeated all the steps to make sure my sourcetree is set for API-Token authentication, with it confirming that Authentication is OK. But still I am not able to access bitbucked during the Brownout Windows.
Attached screen grabs of the relevent parts of sourcetree.
Assisance would be greatly appreciated.
Hi @RobertStephenson – Welcome 
I recommend asking your question over in the Bitbucket users forum. Questions and answers around Bitbucket | Atlassian Community
That forum already has several threads on CHANGE-3222 and the brownouts: Search - Atlassian Community
There’s one common problem people are describing that might be relevant to you: If your old app password is cached in Windows Credential Manager, macOS Keychain, etc, then Git will continue sending the cached password, even if you have an API token configured in Sourcetree. That might cause the behavior you’re seeing.
Good luck!
Hi @AaronMorris1, My apologies for posting in the wrong location and thank you for the links to the correct location
