How Does CopyStorm Handle Daylight Savings?

CopyStorm includes logic specific to Daylight Savings or Summer Time changeovers.

This logic accommodates both time changes and Salesforce record commit latency issues.

When a CopyStorm job finishes within a few hours of a time change, the next job will re-query for records modified before the time change.

The next job will re-scan an extra 90 minutes of record changes prior to the time change. This ensures that Salesforce commit latency issues and time change issues do not cause missing records in the database.

Jobs that run near a time change will take longer to complete.

This is because the job intentionally reads extra data to ensure that all records are copied. As a result, you will likely see a higher number of “Skipped” records – the job is re-checking data that is already up to date in the CopyStorm database.