Alteryx Server Knowledge Base

Definitive answers from Server experts.

TGAL-6394: Daylight Savings Time alters future interval scheduling of jobs and workflows

AlanY
Alteryx
Alteryx
Created

Issue

  • Schedules that are set to run between 2:00:00 am - 2:59:59 am the morning Standard Time changes to Daylight Time (spring-forward) are rescheduled to run at 3:00 am.  This issue does not occur when Daylight Time changes back to Standard Time (fall-back).
    • Subsequent runs of recurring schedules will be based on the 3:00 am run time.
      • If you have a daily recurring schedule set to run at 2:30 am, it will change to run daily at 3:00 am.
      • If you have an hourly recurring schedule set to run at 30 minutes past the hour, it will change to run at the top of every hour.
 
  • Recurring schedules run at an incorrect interval during the Standard Time to Daylight Time changes in both directions.  Intervals are calculated on last run time, not in real-time.
    • If you have a recurring schedule set to run every 2 hours at the top of the hour.
      • During the change from Standard Time to Daylight Time (spring-forward).  The interval during the time change will only be one hour.
        • If the schedule runs at 1:00 am, the next run time is set to 3:00.  During the time change, there is only 1 hour between 1:00 am and 3:00 am since clocks go from 1:59 am to 3:00 am.
      • During the change from Daylight Time to Standard Time (fall-back).  The interval during the time change will be three hours.
        • If the schedule runs at 1:00 am, the next run time is set to 3:00 am.  During the time change, there are 3 hours between 1:00 am and 3:00 am since clocks go from 1:59 am to 1:00 am.
 

Environment Details

 
  • Alteryx Server
    • All Versions


Cause

The Alteryx Service references Gallery node system time which in turn results in incorrect handling of schedules that occur during Daylight Saving Time changes. 



Resolution

 

Solution A (Recommended)

  • Update or recreate schedules after Daylight Saving Time change to run at the preferred time.  


Solution B (Not recommended in most cases)

  • Prior to Daylight Saving Time change, update all server machine system times to use a time zone that does not use Daylight Saving Time (UTC is recommended).
    • If the server machine system times are changed after the Daylight Saving Time change, you will still need to update or recreate affected schedules.
  • IMPORTANT: Use extreme caution when performing this solution.  If you are changing your server machine system times from a time zone that uses Daylight Saving Time, to a time zone that does not use Daylight Saving Time (or vice-versa), you may encounter TGAL-6394 which may alter the scheduled run times of all your schedules.  It's highly recommended that you test this solution in a test environment before performing it in a production environment.


Additional Resources

No ratings