PDF
Download PDF
Download page Viewing and Evaluating Error Messages.
Viewing and Evaluating Error Messages
The Run History tab allows you to view sync details for any sync and to investigate errors that have occurred for any during data sync operations in the list. From the list under Run History, you can view basic sync information and error details and suggested action to take. You can also drill down to the object level to view status for any object in the sync and download a list of error messages if needed for troubleshooting purposes.
To view and evaluate error messages in Run History
- Go to the Run History tab.
- Locate a Sync Id with the status Failed.
- Click the error ( ) icon. A dialog is displayed with a list of errors and suggestion actions to take.
The following table summarizes errors that can occur during a sync operation and suggested actions to take to resolve these errors.
Message | Suggested Action (Consumer Admin) |
---|---|
Unable to sync data to the Consumer Database. | Click "Sync Now" on the Sync Settings page to retry data sync. If the problem persists, please contact Conga Technical Support (you will need to provide the Sync Id). |
An internal error has occurred with the Data Sync service. | Click "Sync Now" on the Sync Settings page to retry data sync. If the problem persists, please contact Conga Technical Support (you will need to provide the Sync Id). |
Unable to fetch Consumer Profile. | Contact Conga Technical Support with the Sync Id. |
Unable to create bulk job on Salesforce. | Click "Sync Now" on the Sync Settings page to retry data sync. If the problem persists, please contact Conga Technical Support (you will need to provide the Sync Id). |
Unable to get initial results from Salesforce. | Please check that all objects in Sync Settings have read access. If the problem persists, please contact Conga Technical Support (you will need to provide the Sync Id). |
Error occurred while retrieving the records from Salesforce. | Please check that all objects in Sync Settings have read access. If the problem persists, please contact Conga Technical Support (you will need to provide the Sync Id). |
Unable to sync data to the target endpoint. | Click "Sync Now" on the Sync Settings page to retry data sync. If the problem persists, please contact Conga Technical Support (you will need to provide the Sync Id). |
Unable to fetch Data using the target object | Please contact Conga Technical support with the Sync Id. |
Unable to sync data to the target endpoint. | Please contact Conga Technical support with the Sync Id. |
Unable to delete data from the target endpoint. | Please contact Conga Technical support with the Sync Id. |
SFDC Api Limit exceeded | It may take up to 24 hours to restore SFDC Api limit. After the limit is restored retry the sync. If the problem persists, please contact Conga Technical Support (you will need to provide the Sync Id). |
Metadata sync of an object failed | Retry data sync. If the problem persists, please contact Conga Technical Support (you will need to provide the Sync Id). |
Consumer profile sync of an object failed | Retry data sync. If the problem persists, please contact Conga Technical Support (you will need to provide the Sync Id). |
To download a list of record-level errors
- Click the Sync Id link for a sync with status 'Failed' or 'Partial Success'. The Run Details page is displayed.
- From the list of objects synced, find the objects with Failed or Partial Success status.
- Click the check box to include any errors from an object in the error report. Click the check box to the left of the Object column to select all such objects.
- Click the Error Messages button at the top of the Details list to download a collection ( .zip file) of error messages generated during the sync in JSON format. It generates the .zip file with Consumer Profile Name_<Sync ID>_<DateTime>.zip naming convention and It comprises the following files.
- Summary File: Provides a summary of all the errors, reasons, number of records affected for each object, the corresponding number of columns, and resolution steps for each error.
- Details Error File: Provides details at record level in a separate file. This JSON file is created for each object separately.