You are here:
Troubleshoot Salesforce Connector Sync Issues in Salesforce Spiff
If you're experiencing issues synchronizing data with the Salesforce connector in Salesforce Spiff, follow recommended steps to troubleshoot the issues.
Required Editions
| Available in: both Salesforce Classic (not available in all orgs) and Lightning Experience |
| Available in: Enterprise, Unlimited, and Developer Editions |
| Available for an additional cost in: Professional Edition with Web Services API Enabled |
| User Permissions Needed | |
|---|---|
| To troubleshoot a Salesforce connector: | A Spiff user role with these permissions turned on.
|
- Double-check the data in your source system to make sure that the data is stored as expected.
- Verify that the user connected to the data source has access to the data.
- Check the Sync Logs page for recent sync errors. From the Admin menu, select Connectors and then click Sync Logs.
-
From the Syncable Objects page, check the object mapping and connector fields.
- Resync the errored object mapping.
- Look for the object mapping that failed and verify that the connector fields have Sync turned on.
-
Verify that unused fields are turned off.
If every connector field is turned on, Spiff requests data for every field in a record. For better performance, sync only the fields that you need for commission calculations.
For more support, contact Salesforce Customer Support.
If you're troubleshooting a third-party connector, contact your Salesforce account executive, who can help you identify the appropriate support channel.
If you're troubleshooting a Snowflake connector, verify whether any changes occurred in your Snowflake environment before you noticed the sync issues.
Resolve Salesforce Connector Sync Errors in Salesforce Spiff
Troubleshoot common sync issues in Salesforce Spiff.
Note Where possible, we changed noninclusive terms to align with our company value of Equality. We maintained certain terms to avoid any effect on customer implementations.
| Error Name | Explanation | Troubleshooting Steps |
|---|---|---|
| ClientNeedsToReAuth | Reauthenticate the Salesforce connector and run a global re-sync. | See Updating a Salesforce Connector in Salesforce Spiff. |
| MissingObjectsInS | A mapping in Spiff expects an object in Salesforce. Either someone deleted the object or you no longer have access to it. | Verify that the object still exists in Salesforce and that you have access to it. If the object has been deleted, turn off sync for the object. See Updating a Salesforce Connector in Salesforce Spiff. |
| InvalidWhereString | The SOQL WHERE expression for limiting the number of records that Spiff syncs from a connected Salesforce object is invalid. |
Spiff performs safety validation of your WHERE clause, but doesn’t validate that the clause returns any data. To test whether your clause returns the results you expect, enter a clause, sync data, check your sync logs for errors, and iterate if necessary. We recommend that only developers with SOQL experience implement this filter. |
| SalesforceAPIError | Spiff tried to sync data with Salesforce, but a timeout occurred before a response was received. | Check the Salesforce Trust Status website for outages or scheduled maintenance. Then, re-sync individual objects with errors, or try a global re-sync. If errors persist, go to the Syncable Objects page and verify that unused fields are turned off for an with errors object. |
| TooManyConnectorFields | If every connector field is turned on for an object, Spiff requests data for every field in a record, which takes longer and limits performance. If too many fields are requested, the query can't complete. | Go to the Syncable Objects page and verify that unused fields are turned off for an with errors object. Then, re-sync individual objects that with errors, or try a global re-sync. |
| TooManyDeletes | Salesforce REST API limits the number of delete operations in a single request. Spiff shows an error when the linked Salesforce environment exceeds this limit. | Contact your Salesforce account executive for help with identifying deleted records that the sync operation missed. |
| BadSpiffOverwrite | A required external_id was overwritten with an invalid value. | Go to the record where the overwrite occurred and replace it with a valid external_id. Then, re-sync. |
| ClientNeedsToWhitelistIP | Spiff is outside of your Salesforce connected app allowed IP range. | Try relaxing your connected app's IP restrictions. See Manage OAuth Access Policies for a Connected App. If you don't want to change the connect app's IP restrictions, set a trusted IP range for Spiff. See Configure Trusted IP Ranges for a Connected App. |
| Unknown | An unidentified error occurred and there's no specific remediation. | Try syncing again. If the issue persists, contact your Salesforce account executive. |
Did this article solve your issue?
Let us know so we can improve!
