# 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.

## What Does CopyStorm Do?

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.

## What’s the Impact?

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.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://learn.capstorm.com/frequently-asked-questions/how-does-copystorm-work/how-does-copystorm-handle-daylight-savings.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.