# Troubleshooting

If you encounter any of the following issues or errors, SailPoint recommends that you follow the guidance provided below to resolve the error before contacting SailPoint Support.

For issues or errors that are not addressed in this connector guide, refer to the following resources for troubleshooting information:

- [SailPoint Identity Services Documentation](<https://documentation.sailpoint.com/saas/help/index.html>)
- [SailPoint Support Knowledge Base](<https://support.sailpoint.com/csm?id=kb_view2&amp;kb_id=05ff44289f011200550bf7b6077fcfa3>)
- [SailPoint Developer Community](<https://developer.sailpoint.com/>)

## Debug Logs

For information about managing additional source settings, including debug logging and downloading connector logs, refer to [Managing Additional Settings](<https://documentation.sailpoint.com/saas/help/sources/managing_additional_settings.html>).

## Test Connection fails for Bitbucket Cloud

**Resolution**: Confirm that **Atlassian Account Email** belongs to the account that owns the **Bitbucket API Token**. Confirm that the token includes `read:workspace:bitbucket` and that the account can access at least one workspace.

## Test Connection fails for the Atlassian organization

**Resolution**: Confirm that **Atlassian Organization ID** identifies the organization that owns the Bitbucket workspaces. Confirm that the organization API key is valid and includes `read:groups:admin`, `read:accounts:admin`, and `read:directories:admin`.

## Workspace Filter does not load workspaces

**Error**: `` `{ExceptionType=sailpoint.connector.ConnectorException, LocalizedMessage=[ConnectorError] error receiving response from connector: stream client connection is broken (connector process may have crashed) (requestId: 138548c59c924bcca257af43bb895410)}` ``

**Resolution**: Save a valid **Atlassian Account Email** and **Bitbucket API Token**. Then select **Test Connection** or refresh the workspace list.

## Pipeline variables are missing

**Resolution**: Confirm that the Bitbucket API token includes `read:pipeline:bitbucket`. For repository-scoped pipeline variables, confirm that the token also includes `read:repository:bitbucket`.

## Secured pipeline variable values are missing

**Resolution**: Bitbucket omits secured pipeline variable values from API responses. No action is required.