Guides
System StatusRaise a TicketZluri Website

Troubleshooting

Salesforce Form-Based Integration Troubleshooting Guide

This page contains a list of common errors and known issues encountered while integrating Salesforce (Form-Based) 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

When does this error occur?

  • While connecting Salesforce to Zluri with an invalid Consumer Key or Consumer Secret.

How to resolve:

  1. Verify your Consumer Key and Consumer Secret are correctly copied from your Salesforce Connected App.
  2. Ensure there are no extra spaces or missing characters when entering the credentials.
  3. Follow the setup guide to properly configure your Salesforce Connected App:
    • Navigate to Setup → App Manager → New Connected App
    • Enable OAuth settings and configure the required scopes
  4. Copy the Consumer Key and Secret exactly as displayed in Salesforce.

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

When does this error occur?

  • When the Consumer Key or Consumer Secret has been regenerated or revoked in Salesforce after the initial connection.

How to resolve:

  1. Check if your Connected App credentials have been modified in Salesforce.
  2. If regenerated, obtain the new Consumer Key and Consumer Secret.
  3. Reconnect the integration using the updated credentials.

SAL-101-A: Login failed: The credentials provided are invalid. Please check your username and password and try again

When does this error occur?

  • While connecting Salesforce to Zluri with incorrect username, password, or security token.

How to resolve:

  1. Verify your Salesforce username is correct.
  2. Ensure your password is accurate.
  3. Check that your Security Token is valid:
    • If you don't have a security token, reset it by going to Settings → Reset My Security Token
    • The security token will be sent to your registered email
  4. Remember that the integration uses: password + security token as the combined password.

SAL-101-B: The credentials used for this integration is expired/revoked. Please ensure that you use the right credentials before reconnecting the integration

When does this error occur?

  • When the Salesforce user's password has been changed or the security token has been reset after the initial connection.

How to resolve:

  1. If your password was changed, use the new password when reconnecting.
  2. If you reset your security token, obtain the new token from your email and reconnect.
  3. Ensure the user account is still active and has the necessary 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

When does this error occur?

  • When your Salesforce organization doesn't have API access enabled.
  • Important: Web Services API are not available for Essentials and Professional Edition Salesforce Organizations.

How to resolve:

  1. Check your Salesforce Edition:

    • This integration requires Enterprise, Performance, Unlimited, or Developer Edition
    • Professional and Essentials editions do not support API access

  2. If you have a supported edition:

    • Contact your Salesforce administrator to enable API access
    • Ensure your organization has sufficient API call limits
    • Verify that API access hasn't been restricted by your administrator

SAL-102-B: Access denied: The API is not available for your organization. Please contact your administrator to request access or check your organization settings

When does this error occur?

  • When API access that was previously available has been disabled or restricted after the initial connection.

How to resolve:

  1. Contact your Salesforce administrator to restore API access for your organization.
  2. Check if any recent security policy changes have restricted API access.
  3. Verify that your Salesforce license still includes API access.
  4. 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 and reconnect the integration

When does this error occur?

  • When the OAuth token generated during connection becomes invalid or is malformed.

How to resolve:

  1. This usually indicates an issue with the OAuth flow or session timeout.
  2. Try reconnecting the integration with fresh credentials.
  3. Ensure your Salesforce session hasn't expired during the connection process.
  4. If the issue persists, verify that OAuth flows are enabled in your Salesforce org:
    • Navigate to Setup → OAuth and OpenID Connect Settings
    • Enable Allow OAuth Username-Password Flows

SAL-103-B: The token used to connect this integration is expired/revoked. Generate a new token and reconnect the integration

When does this error occur?

  • When the OAuth token has expired or been revoked after a successful connection.

How to resolve:

  1. Reconnect the integration to generate a new OAuth token.
  2. Check if the Connected App permissions have been modified or revoked.
  3. Verify that the user who authorized the integration still has access to the Connected App.
  4. 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

When does this error occur?

  • When the connecting user lacks permissions to access user data in Salesforce.

How to resolve:

  1. Ensure the connecting user has one of the following permissions:

    • System Administrator profile
    • View All Users permission
    • Custom permission set with View All Data or Modify All Data

  2. Contact your Salesforce administrator to:

    • Assign appropriate permissions to your user
    • Create a dedicated integration user with necessary permissions

SAL-104-B: The permission for the user who connected the integration is modified/revoked. Modify the user permission and reconnect the integration

When does this error occur?

  • When the user's permissions have been changed after the initial connection.

How to resolve:

  1. Restore the necessary permissions to the connecting user.
  2. Alternatively, reconnect using a user with appropriate permissions.
  3. Consider creating a dedicated service account for integrations to avoid permission changes.

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

When does this error occur?

  • When the connecting user cannot access LoginHistory objects in Salesforce.

How to resolve:

  1. Ensure the user has View All Data permission or System Administrator profile.
  2. Alternatively, assign a permission set that includes access to LoginHistory objects.
  3. Contact your Salesforce administrator to grant the necessary permissions.

SAL-105-B: The permission for the user who connected the integration is modified/revoked. Modify the user permission and reconnect the integration

When does this error occurs?

  • When permissions to access LoginHistory have been removed after connection.

How to resolve:

  1. Restore the View All Data permission or assign System Administrator profile.
  2. Reconnect the integration after restoring permissions.

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

When does this error occur?

  • When the connecting user lacks access to PermissionSetLicense objects.

How to resolve:

  1. Grant the user View All Data permission or System Administrator profile.
  2. Ensure the user can access PermissionSetLicense objects through appropriate permission sets.

SAL-106-B: The permission for the user who connected the integration is modified/revoked. Modify the user permission and reconnect the integration

When does this error occur?

  • When access to PermissionSetLicense objects is revoked after connection.

How to resolve:

  1. Restore permissions to access PermissionSetLicense objects.
  2. Reconnect the integration with restored permissions.

SAL-107-A: The SubDomain used to connect the integration is invalid. Please ensure that you use the right SubDomain to connect the integration

When does this error occur?

  • When an incorrect MyDomain subdomain is provided during connection.

How to resolve:

  1. Locate your correct subdomain:

    • If your Salesforce URL is https://yourcompany.salesforce.com
    • Your subdomain is: yourcompany

  2. For MyDomain users:

    • Check your Salesforce login URL
    • Extract only the subdomain portion (the part before .salesforce.com or .my.salesforce.com)

  3. If you don't use MyDomain:

    • Leave the subdomain field empty
    • The integration will use the default Salesforce login endpoint

SAL-107-B: The SubDomain used to connect the integration is invalid. Please ensure that you use the right SubDomain to connect the integration

When does this error occur?

  • When your Salesforce domain has changed after the integration was connected (which is rare).

How to resolve:

  1. Verify that your Salesforce organization domain hasn't changed.
  2. Check if your organization has been migrated to a new instance.
  3. Contact Salesforce support if you suspect a domain change has occurred.
  4. 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

When does this error occur?

  • When the specified license types don't exist in your Salesforce organization or no users have those license types.

How to resolve:

  1. Verify license types in your organization:

    • Go to Setup → Company Information → User Licenses
    • Note the exact names of available license types

  2. Check license type names:

    • Ensure license type names are spelled correctly
    • License type names are case-sensitive
    • Use comma-separated values for multiple license types

  3. Common license types:

    • Salesforce (for full Salesforce licenses)
    • Salesforce Platform (for Platform licenses)
    • Check your specific org for available types

  4. If filtering by license types is not needed:

    • Leave the License Types field empty to sync all users

SAL-108-B: The License Types used during the connection of this instance are no longer relevant. Please reconnect with valid License Types

When does this error occur?

  • When license types specified during connection are no longer available or assigned in your organization.

How to resolve:

  1. Review current license types in your Salesforce organization.
  2. Update the license types filter with currently available and assigned license types.
  3. Reconnect the integration with valid license types.

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