Error 8
Integration version mismatch
This error occurs when integration issues arise because the Salesforce and Service Board versions are incompatible. You can resolve the error in various ways, depending on your organization's unique needs. In failed HTTP Notification records, the following commands are available on the Option menu.
Resolve Version Mismatch - Keep Service Board Data:
The integration version value of the relevant Service Board record is overwritten with the corresponding value from Salesforce.
The status for the current failed HTTP Notification record is changed to Pending, which initiates an automatic retry.
The status for all FAILED and QUEUED Outbound Queues for the corresponding Salesforce record is set to Completed.
* 
When you use this option, only the integration version number is taken from Salesforce, and all Service Board data is then synced to Salesforce. You must reapply any data that you want to preserve in Salesforce and synch the records back to Service Board. In cases where you must preserve all record updates in Salesforce, follow the manual steps in this procedure instead of using menu commands.
Resolve Version Mismatch - Keep Salesforce Data:
The data in the relevant Service Board record is overwritten by that of the corresponding Salesforce record.
The status for the current failed HTTP Notification record is changed to Outdated.
The status for all FAILED and QUEUED Outbound Queues for the corresponding Salesforce record is set to Completed.
* 
When you use this option, all Service Board data is overwritten by Salesforce data. In cases where you must preserve all record updates in Service Board, follow the manual steps in this procedure instead of using menu commands.
To resolve Error 8:
1. Confirm that the installed SVMXSB package version for your tenant is the latest version, and upgrade if needed.
2. To resolve version mismatch errors by using menu commands, in Max Designer, open the relevant HTTP Notification record, and then in the top right corner, in the Option () menu, click one of the following:
Resolve Version Mismatch - Keep Service Board Data
Resolve Version Mismatch - Keep Salesforce Data
3. To manually resolve version mismatch errors, preserve Salesforce data, and overwrite the Service Board tenant record with the data from the linked Salesforce record, on the Salesforce side, retry the FAILED Outbound Queues for the relevant Salesforce record, and then on the Service Board side, change the status for all related FAILURE and PENDING HTTP notifications to OUTDATED.
4. To manually overwrite the Salesforce record with the data from the linked Service Board record, on the Service Board side, in the HTTP Notification object, make the Request Body field editable, and update the Version field with the same version number as the Salesforce org.
5. Disable all Service Board notifications and make the Version field editable for the failed record objects, and then update the field with the same version number as the Salesforce org,
6. Enable notifications and change the status of failed HTTP Notification records to Pending.
7. On the SFDC side, change the status for all FAILED and QUEUED Outbound Queues for the relevant SFDC record to Completed.
* 
To resolve integration version mismatch errors for multiple HTTP Notification records, you can use Mass Update.
For more information:
Was this helpful?