Data Sync Settings

Data Sync Settings


 

 

 

 

 

Name

Max Sync Waves

Key

pulsar.sync.maxWaves

Value

A Positive Number

Default Value (if any)

24

Compatibility

iOS
Windows
Android

Description

A sync wave is generally equivalent to one month of history, and with this numeric setting you may specify how many months into the past (in terms of active records) that the algorithm should look back and fetch them. Pulsar determines active records by using the LastModifiedDate, SystemModStamp, or another datetime field (if overridden with the pulsar.sync.objects.lastModifiedDateField Pulsar Setting).

The first wave is calculated from the current timestamp back to the first day of the same month. This means that the first wave is often less than a full month’s worth of data. This is done to break up the remaining waves in simple month segments. For example, specifying 4 waves and performing an initial sync on December 5 will create one wave from December 1 to December 5, a second wave encompassing all of November, and a third wave encompassing all of October. The fourth and final wave will attempt to retrieve as much data as possible from September 30 to as far back as January 1, 1980. Please see the pulsar.sync.enableFullHistoryWave setting for more information on customizing the behavior of the final wave.

Notes/Comments

To guarantee that a user should initially sync a specific number of months of historical data, you will need to add one or two to your number depending on how you’ve configured the final wave. For example, for a minimum of two years worth of data, you can specify 26 (with the full history wave enabled) or 25 (with the full history wave disabled).