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

## Known Issues

These are known issues and will be fixed in an upcoming CyberArk Release

- CyberArk Groups API for User association doesn't work properly when Org is assigned to Groups.
- CyberArk Groups API for User association doesn't work when Groups are hierarchical (Parent-Child) relationship.

## Direct Permissions not visible after Entitlement Aggregation

Direct permissions are not aggregated and do not appear in the Permissions tab of entitlements after entitlement aggregation.

**Resolution:** To resolve this, the customer needs to run an unoptimized entitlement aggregation. For example:

```text
curl --location 'https://tenantname.api.cloud.sailpoint.com/beta/sources/source_id/load-entitlements?disableOptimization=true' \ --header 'Authorization: Bearer <Token>' \ --header 'Content-Type: application/x-www-form-urlencoded' \ --data-urlencode 'disableOptimization=true'
```

> [!NOTE]
>
> If the issue persists, set `useGroupAggregationWithoutFilter` to **true** in `source.xml` and run an unoptimized entitlement aggregation.