*****UPDATE*****
During testing we found that we had issues creating bookings given the examples below. If you look the timeline of the booking manager, you can see the time jumps from 1:59am to 3:00am (as expected). As a results, attempts to create booking with a preroll time between 2:00am and 2:59am fail since that time doesn't exist. MITIGATION: our original plan was to modify the pre-roll times on the bookings to account for the offset, but instead we're going to change the start time on the schedule so the booking can create.
ORIGINAL POST
With Daylight savings time approaching in the US this weekend, just wanted to confirm that we'll be OK for an SRM scenario...
We have two events on Sunday morning, one that starts at 3:00a with a 2:30a pre-roll and one that starts at 3:15a with a 2:45a pre-roll. Since the time change will go from 2:00am straight to 3:00am and thus skipping past the 2:30a and 2:45a pre-rolls, is there anything that needs to be done in advance to prepare for this? Or, does SRM have the necessary awareness of DST to handle these bookings to make sure the pre-rolls start?
Thanks!
Internally dates are stored in UTC, so in fact your events will trigger in the UTC time no matter what time zone you have defined.
You will need to check if the times in UTC times are correct, or if some adjustment is needed.
Thanks Jorge, we were trying to test in the staging environment how this would behave by creating some test bookings and changing the server clock to just before 2a EST to see what would happen. Unfortunately, the time settings are locked down and we couldn’t. To be safe, we’ve opted to start both bookings at 1:59a EST to make sure they fire up prior to the change. In the meantime, we have test bookings setup in the staging environment so we can see how they handle the change. I will follow up with the results.