# 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>).

## Provisioning for group and permission profiles is not working properly

**Resolution**: When use cases are executed, the following behaviors determine whether provisioning is or is not supported on the connector end.

**Group Entitlement**

- Supported when the provisioning (add/remove) of a single test group is executed.
- Removal of the Administrator and/or Everyone group is not supported.

**Permission Profile**

- Supported when the user has one permission profile.
- Removal of the permission profile is not supported, however, it can be replaced with a new permission profile.

## 400 Bad Request error during test connection

This happens when your consent is not provided in the DocuSign application to the client (SailPoint) application.

**Resolution**: Ensure that you provide user consent with the required scope of "signature impersonation." For more information, refer to the "Step 1: Request application consent" section from the [DocuSign documentation](<https://developers.docusign.com/platform/auth/jwt/jwt-get-token/>).
