KNOWLEDGE BASE

Scheduled Hourly Tasks Running on The Hour Regardless of Assigned Start Times


Published: 06 Nov 2019
Last Modified Date: 07 Nov 2019

Issue

Admin schedules unexpectedly run at different time than what they were originally set. The following scenario may apply to you: 
  • 24 hours schedule - A task that is scheduled to run every hour starting and ending at the same time (for example, starting at 3:30 AM and ending at 3:30 AM) is queued to run starting on the hour, even when scheduled to start at the :15, :30 or :45. In other words, the jobs will start at 3:00 AM, 4:00 AM, 5:00 AM etc and not at 3:30 AM, 4:30 AM, 5:30 AM. 
  • Overnight hourly schedule -  A task that is scheduled to run every hour starting before midnight and ending midnight (For example, starting at 10:30 PM and ending at 8:30 AM) is queued to run starting on the hour before midnight, even when scheduled to start at the :15, :30 or :45. In other words, the jobs will start running at 10:00 PM, 11:00 PM, midnight, 1:30 AM , 2:30 AM etc rather than 10:30 PM, 11:30 PM, 12:30 AM, 1:30 AM , 2:30 AM etc.

Environment

  • Tableau Server 2019.4 
  • Tableau Online

Resolution

Resolutions for 24 hours schedule scenario

  • Option 1: Change the schedule to start at 12:15, 12:30, or 12:45 AM and end at 12:00 AM. Note that this adjustment does not change the actual number of times a task will run in a day. 
  • Option 2 (for Tableau Server only): Use TSM to set backgrounder.admin_schedules_use_cron_strings to false to turn off the configuration. For more information, see TSM command line reference

Resolution for overnight hourly schedule scenario

  • Option 1: Split the schedule into two separate schedules. Create one schedule from :15/30/45 to midnight, then create a second schedule from 12:15/30/45 AM to end time.
  • Option 2 (for Tableau Server only): Use TSM to set backgrounder.admin_schedules_use_cron_strings to false to turn off the configuration. For more information, see TSM command line reference

Cause

This behavior is related to known issues with IDs 1022748 and 1022552 which are currently under investigation. 
Did this article resolve the issue?