If you received an email notification that your Salesforce connection encountered an error, we're here to help you figure out how to get back up and running. In some cases, reauthorizing your connection will solve the problem (think of it like restarting your computer). In other cases, you may need to get in touch with your Salesforce admin or whoever does sales ops to help you change a setting in Salesforce.

Common Errors

The most common errors are the following. Find what they mean and how to troubleshoot and fix them below.

1. Over API Quota Limit
2. API_CURRENTLY_DISABLED: API is disabled for this User
3. API_DISABLED_FOR_ORG: The REST API is not enabled for this Organization
4. API_DISABLED_FOR_ORG: limits resource is not enabled
5. invalid_grant: expired access/refresh token
6. invalid_grant: inactive user

1. Over API Quota Limit

What happened? We paused our sync with Salesforce because your Salesforce organization has used up 80% or more of its daily Bulk API quota. (For most companies, many other services besides Crossbeam drive the majority of this quota usage.) We pause our sync at this percentage as a safety precaution so we don't push your organization over its limit and interfere with critical Salesforce functionality. We'll try to sync again the next day when the limit is reset.


What does the error look like?

Below is an example of the error.

Salesforce has reported 189737/218000 (87%) total REST API quota used across all Salesforce Applications. Terminating data sync to not go past configured percentage of 80% total quota. 

What do I do? If this is your first time getting this error, then you may not need to do anything. If you've received this error more than once, it may be time to reach out to your sales ops team to see what all is impacting your Bulk API quota limit.

2. API Current Disabled

What happened? We were unable to sync with Salesforce because the user that authenticated Salesforce does not have API access in Salesforce.

What does the error look like?

Below is an example of the error.

API_CURRENTLY_DISABLED: API is disabled for this User

What do I do? You can reauthorize the Salesforce connection with a user that has API access, or you can ask your Salesforce admin to give API access to your existing user in Salesforce.

API Disabled for Org

Below are two variations of this error.

3. API_DISABLED_FOR_ORG: The REST API is not enabled for this Organization

What happened? We were unable to sync with Salesforce because your Salesforce organization does not have API access.

What was the error?

Below is an example of the error.

API_DISABLED_FOR_ORG: The REST API is not enabled for this Organization.

What do I do? You will need to reach out to your Salesforce admin to ensure your Salesforce org has API access.

4. API_DISABLED_FOR_ORG: limits resource is not enabled

What happened? We were unable to sync with Salesforce because your Salesforce organization does not have API access properly configured.

What was the error?

Below is an example of the error.

API_DISABLED_FOR_ORG: limits resource is not enabled   

What do I do? You will need to reach out to your Salesforce admin to ensure your Salesforce org has both the API enabled and "View Setup and Configuration" system permissions enabled. This error is likely because do not have "View Setup and Configuration" system permissions enabled.

Invalid Grant

Below are two variations of this error.

5. Invalid_grant: expired access/refresh token

What happened? We were unable to sync with Salesforce because we no longer have access to your Salesforce instance.

What was the error?

invalid_grant: expired access/refresh token 

What do I do? You will need to reauthorize your Salesforce connection in Crossbeam.

6. Invalid_grant: inactive user

What happened? We were unable to sync with Salesforce because the user who originally connected Salesforce to Crossbeam does not have access to Salesforce anymore. The user may have been deactivated or removed from the org.

What was the error?

invalid_grant: inactive user 


What do I do? You can reauthorize the Salesforce connection with a new user, or you can ask your Salesforce admin to verify that the user that is currently authenticated has access to your Salesforce org.

Did this answer your question?