Tackle for Salesforce writes the latest AWS, Microsoft, and Google Cloud co-sell sync errors directly into Salesforce, so your team can troubleshoot failed updates without leaving Salesforce.
Requirement: This feature requires Tackle for Salesforce version 2.9 or later. See 'Salesforce integration release information and version types' to confirm your version and learn how to upgrade.
View the latest sync error on a record
Tackle writes sync error information to these records:
Tackle AWS Co-sell Opportunity
Tackle GCP Opportunity
Tackle MSFT Referral
Each record includes:
Last Cloud Sync Error — the most recent sync failure message.
Sync Error Type — the category of the error.
Sync Error Date/Time — when the error occurred.
Full Error Detail — the complete error text from the cloud marketplace.
Open any Tackle AWS Co-sell Opportunity, Tackle GCP Opportunity, or Tackle MSFT Referral record in Salesforce and look for these fields in the record detail layout.
Salesforce record layout showing Last Cloud Sync Error, Sync Error Type, Sync Error Date/Time, and Full Error Detail fields
Report on sync errors
Because sync error fields are standard Salesforce fields, you can:
Add them to list views to quickly scan for records with recent errors.
Build reports that filter or group by sync error type, so RevOps and Alliance teams can monitor sync health across all co-sell records.
Submit multiple Microsoft co-sells at once
In Salesforce, Microsoft co-sells are created as drafts first, then submitted to the cloud. This bulk action lets you submit several draft co-sells to Microsoft at the same time, and quickly see which ones synced successfully and which had errors.
Note:
Bulk-create job results and retry are currently available for Microsoft co-sells only.
After running a bulk submit job, open the job results.
Review which records were submitted successfully and which failed.
For each failure, check the listed reason to understand what needs to be corrected.
Retry a failed bulk-created co-sell
In the bulk-create job results, find a failed record.
Correct the underlying Salesforce data indicated by the failure reason.
Select Submit to resubmit the record.
Note:
This applies to Microsoft co-sells submitted via this bulk action only. Submitting again doesn't automatically repair mismatched field mappings — correct the source data first, then submit.
For AWS and Google Cloud co-sells: Identify and fix failed co-sells directly from the bulk-create co-sells job results in Salesforce:
After running a bulk-create job, open the job results.
Rows with an Error badge indicate a failure — hover over the badge to see the reason
Select View co-sell to open that specific co-sell record.
Correct the underlying issue, then submit the co-sell again.
Related articles: