Troubleshooting
This page contains a list of common errors and known issues encountered while integrating Salesforce-v2 with Zluri, and instructions on how to fix them.
If your issue isn’t mentioned here, feel free to submit a ticket or contact us directly at [email protected].
SAL-100-A: The client key or client secret used to connect the integration is invalid. Please ensure that you use the right client key or client secret to connect the integration
This error occurs when the OAuth client credentials provided during the connection setup are incorrect or invalid.
To resolve this error:
- Verify that you have copied the Client ID and Client Secret correctly from your Salesforce Connected App
- Ensure there are no extra spaces or missing characters in the credentials
- Make sure you're using credentials from the correct Salesforce environment (production vs sandbox)
- If you're unsure about the credentials, regenerate them in Salesforce and try connecting again
SAL-100-B: The client key or client secret used for this integration is expired/revoked. Please ensure that you use the right client key or client secret before reconnecting the integration
This error occurs when the OAuth client credentials that were working previously have been revoked or expired.
To resolve this error:
- Check if the Connected App in Salesforce is still active and hasn't been deleted or disabled
- Verify that the credentials haven't been regenerated by another administrator
- Generate new client credentials from your Salesforce Connected App and reconnect the integration
SAL-101-A: Login failed: The credentials provided are invalid. Please check your username and password and try again
This error occurs during the OAuth authorization flow when the Salesforce login credentials are incorrect.
To resolve this error:
- Verify that you're using the correct username and password for your Salesforce account
- Ensure you're logging into the correct Salesforce environment (production, sandbox, or custom domain)
- If your organization uses two-factor authentication, make sure to complete the authentication process
- Try logging into Salesforce directly in a browser to verify your credentials work
SAL-101-B: The credentials used for this integration is expired/revoked. Please ensure that you use the right credentials before reconnecting the integration
This error occurs when the Salesforce user account that authorized the integration has been deactivated or had its credentials changed.
To resolve this error:
- Verify that the user account used for the integration is still active in Salesforce
- Check if the user's password has been reset or expired
- If the user account is no longer available, reconnect the integration using an active user with appropriate permissions
SAL-102-A: Access denied: The API is not available for your organization. Please contact your administrator to request access or check your organization settings
This error occurs when Salesforce APIs are disabled for your organization or the API version is not supported.
To resolve this error:
- Contact your Salesforce administrator to enable API access for your organization
- Verify that your Salesforce edition supports API access (Professional, Enterprise, Unlimited, or Developer editions)
- Check if API access has been restricted by IP address restrictions or other security settings
- Ensure that the Salesforce REST API is enabled in your organization settings
SAL-102-B: This API which was used earlier for to connect integration is now not available for your organization. Please reconnect the integration after making sure you got the access from your administrator
This error occurs when API access that was previously available has been disabled or restricted after the integration was connected.
To resolve this error:
- Contact your Salesforce administrator to restore API access for your organization
- Check if any recent security policy changes have restricted API access
- Verify that your Salesforce license still includes API access
- Reconnect the integration after confirming API access is restored
SAL-103-A: The token used to connect this integration is invalid. Generate a new token to connect the integration
This error occurs when the OAuth access token provided during connection is malformed or invalid.
To resolve this error:
- Complete the OAuth authorization flow again to generate a new valid token
- Ensure that you're not manually entering or modifying the OAuth token
- Check that the OAuth redirect URI in your Salesforce Connected App matches the one used by Zluri
- Verify that the Connected App has the correct OAuth scopes configured
SAL-103-B: The token used to connect this integration is expired/revoked. Generate a new token and reconnect the integration.
This error occurs when the OAuth access token has expired or been revoked after a successful connection.
To resolve this error:
- Reconnect the integration to generate a new OAuth token
- Check if the Connected App permissions have been modified or revoked
- Verify that the user who authorized the integration still has access to the Connected App
- Ensure that the Connected App is still active and hasn't been deleted
SAL-104-A: The user trying to connect the integration does not have sufficient permissions to read users. Modify the user permission and try again
This error occurs when the Salesforce user attempting the connection lacks the necessary permissions to query user data.
To resolve this error, ensure the user has one of the following:
- System Administrator profile
- View All Users permission
- A custom profile with Read permission on the User object
- Access to the specific license types you want to sync (if using license type filtering)
Contact your Salesforce administrator to grant the appropriate permissions.
SAL-104-B: The permission for the user who connected the integration is modified/revoked. Modify the user permission and reconnect the integration
This error occurs when the Salesforce user who originally connected the integration has lost the required permissions to read user data.
To resolve this error:
- Contact your Salesforce administrator to restore the necessary permissions for the user
- Alternatively, reconnect the integration using a different user with appropriate permissions
- Ensure the user maintains View All Users permission or equivalent access rights
SAL-105-A: The user trying to connect the integration does not have sufficient permissions to view login history. Modify the user permission and try again
This error occurs when the Salesforce user lacks permissions to access login history data.
To resolve this error, ensure the user has:
- System Administrator profile, OR
- View Login History permission
- Read access to the LoginHistory object
Contact your Salesforce administrator to grant the View Login History permission.
SAL-105-B: The permission for the user who connected the integration is modified/revoked. Modify the user permission and reconnect the integration
This error occurs when the user who connected the integration has lost access to login history data.
To resolve this error:
- Contact your Salesforce administrator to restore View Login History permission
- Alternatively, reconnect using a user with System Administrator privileges
- Verify that the LoginHistory object is accessible to the user
SAL-106-A: The user trying to connect the integration does not have sufficient permissions to access permission set licenses. Modify the user permission and try again
This error occurs when the user lacks access to permission set license information.
To resolve this error, ensure the user has:
- System Administrator profile, OR
- View Setup and Configuration permission
- Read access to the PermissionSetLicense object
Contact your Salesforce administrator to grant the necessary permissions.
SAL-106-B: The permission for the user who connected the integration is modified/revoked. Modify the user permission and reconnect the integration
This error occurs when the user has lost access to permission set license data after the integration was connected.
To resolve this error:
- Contact your Salesforce administrator to restore access to permission set licenses
- Reconnect the integration using a user with System Administrator privileges
- Verify that View Setup and Configuration permission is granted to the user
SAL-107-A: The SubDomain used to connect the integration is invalid. Please ensure that you use the right SubDomain to connect the integration.
This error occurs when the domain/subdomain entered in the integration form is incorrect or doesn't exist.
To resolve this error:
- Verify the correct domain for your Salesforce organization
- If your Salesforce URL is
https://mycompany.salesforce.com
, enter onlymycompany
as the domain - For sandbox environments, use the sandbox-specific domain (e.g.,
mycompany--sandbox
) - Ensure there are no typos or extra characters in the domain name
- Check that your Salesforce organization is active and accessible
SAL-107-B: The SubDomain used to connect the integration is invalid. Please ensure that you use the right SubDomain to connect the integration.
This error can occur if your Salesforce domain has changed after the integration was connected (which is rare).
To resolve this error:
- Verify that your Salesforce organization domain hasn't changed
- Check if your organization has been migrated to a new instance
- Contact Salesforce support if you suspect a domain change has occurred
- Reconnect the integration with the correct current domain
SAL-108-A: The provided License Types are either incorrect or not assigned to any users. Please enter valid License Types and try again.
This error occurs when the license types specified in the integration form don't match any users in your Salesforce organization.
To resolve this error:
- Verify the exact names of license types in your Salesforce organization by checking user profiles
- Ensure license type names are spelled correctly and match the case-sensitive format used in Salesforce
- Use comma-separated format for multiple license types (e.g.,
Salesforce,Platform
) - Leave the License Types field empty if you want to sync all users regardless of license type
- Check that the specified license types are actually assigned to active users
SAL-108-B: The License Types used during the connection of this instance are no longer relevant. Please reconnect with valid License Types.
This error occurs when the license types that were valid during connection are no longer assigned to any users.
To resolve this error:
- Review current license assignments in your Salesforce organization
- Check if license types have been changed or users have been reassigned to different licenses
- Reconnect the integration with updated license type names or leave the field empty to sync all users
- Verify that the license types you want to filter by are still active and assigned to users
If your issue is not listed here, please contact Zluri support with the specific error message and steps you've already tried for further assistance.
Updated about 15 hours ago