Common problems with Bitbucket Cloud

When you add the integration

What you see	What to do
Email is required.	Fill in Email with the address of the Atlassian account that owns the token.
api.bitbucket.org refused the credentials (401). Check the token, and that it has not expired. Fix the field above, or save anyway if the source is only unreachable for now.	The email or the token is wrong, or the token has expired. Check Email, then create a new token in Bitbucket and paste it in Token.

The form also offers Save anyway, to keep the token when Bitbucket is only unreachable for now.

After you add it

What you see	What to do
In the token list, in State, the message api.bitbucket.org refused the credentials (401). Check the token, and that it has not expired.	Edit the token: new token, then Test connection.
On Administration › Company connections, Not working on the Bitbucket Cloud card	Open the card: State says why.

Still stuck?

Write to support@forgeit.fr with the message you see.