In order to ensure the batch-data process is not impacted by daylight savings, we recommend setting its scheduled time to the UTC zone.
This is due to the following:
- Optimove’s systems are aligned with the UTC time zone. As a result, our system performs the batch-data process according to UTC time.
- In case your batch-data process is set to a time zone other than UTC, the process' timing might be affected on the day of UTC’s clock change.
Why does this matter?
Optimove’s systems are aligned with the UTC time zone and will not be impacted by the change, meaning Optimove will continue to extract your consumer data at the same time.
However, if your systems are not aligned with the UTC time zone and are configured to local time zones, you will receive the request for data one hour later or earlier, depending on the seasonal clock change.
What should you expect?
If your systems are configured to a local time zone and not on UTC, on the day of the clock change, your batch-data process will begin one hour later than usual.
For example - EST will be changed from UTC-5 hours to UTC-4 hours. Therefore, 10:00 am UTC used to be 5:00 am EST, but will now be 6:00 am EST. Meaning your batch-data process will start at 6:00 am and not 5:00 am.
What can you do?
If your systems can’t be set to UTC time zones, you should reach out to your CSM and inform them of such so that the Optimove team can reschedule the time of your batch-data update accordingly.