Anamoly in Runtime of schedule Job due to daylight savingIssue A scheduled task called 'ProdPlan_Monthly creation of tickets' to process the records in the 'u_prodplan_tickets1' table, follow the task's specified Run Time for each task. According to the 'Run Time' setting, this task should be executed daily at 00:01:00 hours. However, the screenshot indicates that the Run Time was unexpectedly changed to 23:01:00 hours for a few days, despite all the tasks having the same 'Create Date'. CauseIt was observed that the run date field displayed 23:00 instead of 00:00, indicating a difference of one hour. The value is accurate for dates between April and October, but between November and March, it is reduced by one hour.ResolutionIn Database the Run time value is same for all the records, but in User Interface it is showing different. pbrun snow query <instance_name> --timer --timeout-seconds=300 "select u_run_date,sys_id from u_prodplan_tickets1 where sys_id='ed85c737db0410d43d422ded0b961985'" +------+---------------------+----------------------------------+| Port | u_run_date | sys_id |+------+---------------------+----------------------------------+| 3400 | 2020-12-15 14:20:00 | ed85c737db0410d43d422ded0b961985 |+------+---------------------+----------------------------------+ pbrun snow query <Instance Name> --timer --timeout-seconds=300 "select u_run_date,sys_id from u_prodplan_tickets1 where sys_id='2985c737db0410d43d422ded0b96197d'" +------+---------------------+----------------------------------+| Port | u_run_date | sys_id |+------+---------------------+----------------------------------+| 3400 | 2020-07-15 14:20:00 | 2985c737db0410d43d422ded0b96197d |+------+---------------------+----------------------------------+ The Run Time column was verified by adjusting the time to GMT/IST in time zones where Daylight Saving Time is not observed. In time zones where Daylight Saving Time is not applicable, the User Interface displays the correct time. As a result, the jobs will continue to be triggered at the same time, with the system automatically accommodating for Daylight Saving Time.The jobs will be executed according to the correct scheduled time.Related LinksKB0622072: Hourly schedules execute one hour offset when Daylight Saving Time (DST) changes KB0993431: Daylight Timezone Conflict in Scheduled Jobs for Users in Different Time Zones