Interpreting Sync Reports
This section provides some pointers about how to interpret some key aspects of sync reports.
Comparing InProgress entries with Completed / Failed entries
You might see a significant number of sync report records with both InProgress and Completed/Failed status. It is not possible to conclude anything based on absolute/relative numbers of such records. However, the following points can be noted to understand what these mean in a specific org
In general, the date range of these InProgress records and the number of users from whose devices these have been created should help find out the average number of failures per user per day. This average rather than the absolute number of records is a good indicator of whether the number of failures is ok or not. If failures are encountered by only some users and not all, then those users would have reported the issues as their day-to-day usage of the app would have been affected.
Knowing the type / cause of the failure
It is not possible to find out more detail on the type / cause of the failure from ServiceMax Job Log records. As the name of the configuration option and the purpose of the fields in the report imply, the purpose of these log records is to capture the time taken for different types of sync operations and get the count of successful and failed syncs. If the pattern indicates issues with a particular type of sync / user / particular time of day (OOTB reports and additional custom reports created from these log records can be checked to find out this), further investigation can be done for that particular sync / user
Knowing the volume of data synced
As explained above, these sync reports do not capture any information related to volume (size or count of records) of data synced.