Scheduled Jobs "Run Time" and "Next Action" time fields do not match - Known Error

Scheduled Jobs "Run Time" and "Next Action" time fields do not match Description The time shown on the next action and run time do not match when using either the GMT, Hong Kong, or Japan timezone. The time being shown in the next action is an hour before the run time.

For example using the Hong Kong TZ: Next Action: 05:15 Run Time: 06:15

When using other time-zones from the instance the time matches: Using the London TZ: Next Action Time: 22:15 Run Time: 22:15

Steps to Reproduce

1. Login as administrator. 2. Change the instance timezone to either GMT, Hong Kong, or Japan. 3. Go to the sys_trigger table. 4. Select any scheduled job where trigger type is "Daily". Notice the record will show the hour difference in the Next Action and Run Time. 5. Go back to the homepage and change the timezone to US/Pacific or Europe/London. 6. Go back to the sys_trigger table. 7. Select again any scheduled job where trigger type is "Daily". Notice the record will show no difference in the time with the Next Action and Run Time.

Workaround This is expected behaviour, only occurring when users are set in a timezone with daylight savings, since "Run Time" is a GlideTime field, so daylight savings unaware.

"Run Time" can differ by the actual time if the job is created in daylight saving timezone (DST) and viewed in non-DST. For example on June 14th, PST has DST enabled. If a Job is set to run 6PM PST, it will show 2AM UTC and 10AM Hong Kong Time (HKT) while the converted time on this date would be 1AM UTC and 9AM HKT. In any case "Next Action" will show the right time when the job will be run (as anytimezone/anydate), therefore showing differences in "Run TIme" and "Next Action" when PST has DST enabled for example.

There are two possible workarounds. Find the Related Link to Configure Job Definition within the sys_trigger record: 1. Set "Run as" in the sysauto_script record. This value is by default set to the user who created the sysauto_script record. Configure and add the field to the form if not present, and select a user with desired timezone. Ref.: https://docs.servicenow.com/csh?topicname=c_ScheduledJobs.html&version=latest For example, create a user with adequate roles and timezone HKT. Note that this will execute the script with the provided user and with user's timezone. This will result in "Run Time" and "Next Action" time to be the same in HKT timezone. Please note this can affect reports.

2. Change the "Time" in the sysauto_script. You can offset it by 1 hour to match your timezone hours. Please note it will require to be changed again when DST is disabled.

NOTE: The scheduled job executes at the same time for the user who created the sysauto_script record. For example, if created by a user with timezone PST and run at 10AM, it will execute the job at 10AM for all days (with or without DST).