Automation schedule settings change after save with specific combination of timezones and start times on yearly repeat
Last updated 2020-03-10 ·Reference W-4976358 ·Reported By 0 users
When scheduling an automation on yearly repeat, specific combinations of timezone and start times will cause the schedule to change after the automation is saved. This results in a different schedule settings than was intended. Video attached.
Steps to reproduce:
1) Create an automation with a schedule
2) Configure the Start Date of 1/1/2019 at 12:00 AM and any timezone containing GMT-05:00. Set Repeat to Yearly on January 1. Click Done.
3) Observe the starting time display as 1/1/2019 12:00 AM
4) Click Save to save the automation
The schedule start date displayed on the workflow is 2/1/2020 12:00 AM. In dbo.Recurrence, this is what we see:
Will run every January 1, effective 1/01/2019 at 11:00 PM and will occur 1 time(s)
If you edit the schedule subsequently, the starting date is now specified as 2/1/2020 at 12:00 AM. When the automation is saved again without any further schedule edits, this is what is in dbo.Recurrence:
Will run every January 1, effective 1/01/2021 at 11:00 PM and will occur 1 time(s)
The schedule start date displayed on the workflow is 1/1/2019 12:00 AM
Tested combinations that cause the schedule start date to change on save are (but not limited to):
Start date of 1/1 at 12:00 AM with timezone GMT-05:00
Start date of 1/1 at 1:00 AM with timezone GMT-04:00
Start date of 1/1 at 1:00 AM with timezone GMT-03:00
Schedule the automation with a different start hour
Reported By (0)
Any unreleased services, features, statuses, or dates referenced in this or other public statements are not currently available and may not be delivered on time or at all. Customers who purchase our services should make their purchase decisions based upon features that are currently available.