Troubleshoot an Unsuccessful Salesforce Output Connector Run

The CRM Analytics Salesforce Output Connector pushes data from CRM Analytics into a Salesforce org as a Bulk API job. If a portion of the data push fails, use Salesforce Setup and Postman or cURL to troubleshoot.

1. From Setup in the Salesforce org that initiated the job, in the Quick Find box, enter Bulk Data, and then select Bulk Data Load Jobs.
2. Select the job corresponding to your data push.
3. From the information displayed, copy the Job ID and API version. You use this information later to find the failed rows.
   The job ID prefix is 750 for a single job and 751 for a batch job. This guide uses the example of a batch job prefixed by 751.
4. In the Auto-Chunked Batches section, check the Records Failed column and use the API to investigate the failed records.
   

   A row fails because its data couldn’t create or update a record in Salesforce. Several issues can cause this failure, including incorrect date formatting or a mismatch between the source row’s and record field’s datatype.

5. To find which rows failed, create this API URI using your API version and Job ID: /services/data/vXX.X/jobs/ingest/jobID/failedResults/.
   For example, /services/data/v51.0/jobs/ingest/751B000000JLPLt/failedResults/ For more information, see Get Job Failed Record Results.
6. Execute the API call in Postman or using cURL.
   The end of the raw response has a representation of your failed rows starting with sf__Id. The text after the row names is the error reason. For example, here’s a raw response.

   "sf__Id","sf__Error",Id,Account__c,Checkbox__c,Date__c,Text__c,Currency__c
   "","ENTITY_IS_DELETED:entity is deleted:--","a1h5G0000000OhEXTJ","003M000000YAEHJLA5","false","","","41040.0"
   

   The error component is ENTITY_IS_DELETED:entity is deleted.

7. To find successful rows, create the URI based on the instructions in Get Job Successful Record Results.