Agent skipped schedule on one day
We faced an issue where an agent skipped one day in its schedule after a restart.
This has happened on a couple of occasions, it appears to happen when the schedule is updated from machine in a different time zone close to midnight.
Steps to Reproduce
- Require server and client to be in different timezones, for example: MST and EST.
- Create a weekly agent run time to run at 4:30am MST.
- At 11:30pm change the schedule or restart from the EST machine.
- Next run time misses one day.
There was a defect in the weekly pattern next run time calculation when crossing timezones.
0% found this useful