GS Error Logs Object
This article explains how to use the GS Error Logs object to create a report with the list of Timeline activities and the reasons they failed to sync to Salesforce.
Overview
By default, Timeline Activities sync to Salesforce once every four hours. You can also manually sync Timeline activities to Salesforce. However, Timeline Activity sync may fail for various reasons. This article explains how to create a report on Timeline sync failure reasons so that you can easily analyze and rectify the issues that fail the sync process.
The GS Error Logs object can be used to build the report. This object consists of fields which store various information related to the sync error.
To create a Report:
- Navigate to Administration > Analytics > Report Builder.
- Click + REPORT.
- Select GS Error Logs as the source object.
- Add the following fields to the Show me section.
- Name
- Area Name
- Entity Type
- Error Count
- Message
-
Click RUN.
You can find the Activity name and the reason for failure (message field) for each of the activities.
Common Error Messages Encountered
This section describes some common error encountered during the sync process and the reason for those errors.
| Error Code | Reason for the error |
|---|---|
| REQUIRED_FIELD_MISSING | Value for mandatory field is not populated. |
| ENTITY_IS_DELETED | Task/Event object record is deleted. |
| INVALID_CROSS_REFERENCE_KEY | When you provide incorrect ID to a field. For instance, if you provide Opportunity ID for Account ID field. |
| FIELD_CUSTOM_VALIDATION_EXCEPTION | Custom validation rule in field is violated. |
| STRING_TOO_LONG | String length has exceeded the limit. |
| CANNOT_INSERT_UPDATE_ACTIVATE_ENTITY | Can be field level security issue or entity is currently being used in other execution. |
| LIMIT_EXCEEDED | Mostly when there are so many operations are happening in one execution and CPU is completely exhausted. |
| UNABLE_TO_LOCK_ROW | Unable to lock the record which is requested to update. |