Daylight Timezone Conflict in Scheduled Jobs for Users in Different Time ZonesDescriptionFor Scheduled Jobs where the user creating the scheduled job is in a time zone in daylight time, and the "Run as" user is in a time zone without daylight time, one hour gets added to the "Next action" time when the Scheduled Job runs, and the sys_trigger is updated with a new time.Steps to Reproduce Open the System Administrator sys_user record, and set the "Time Zone" to GMT.Set your user profile Time zone to US/Central. Ensure US/Central is under daylight time (daylight savings). If not, chose a time zone that is in daylight time. Navigate to System Definition > Scheduled Jobs. Click "New", and choose "Automatically run a script of your choosing".Add the "Run as" field to the form.Create a new scheduled job with the following parameters: Run: DailyTime zone: -None-Run as: System AdministratorTime: set this to a few minutes in the future Before the job runs, navigate to sys_trigger.list. Observe "Next action" for the job is set correctly to a few minutes in the future.After the job runs, refresh the sys_trigger list. Observe "Next Action" is correctly updated to 1 day in the future, but the time has been changed to 1 hour later.WorkaroundBy design, if "Time zone" is set to None on a scheduled job, its sys_trigger is set to run based on the creating/updating user's time zone, and then rescheduled using the session's time zone (the Run as user's session). This means that the rescheduled time is offset when both users are in different daylight savings times. The possible workarounds are: - Set the "Time zone" of the scheduled job and set the "Time" field for that time zone. This will override the time zone of the "Run as" user when calculating the "Next action" time. OR - Use a "Run as" user with the same time zone as you, or that is in a time zone with similar daylight savings dates as you.Related Problem: PRB1509517