Closed Bug 1347783 Opened 9 years ago Closed 9 years ago

Jobs scheduled @weekly skipped 2017-03-12

Categories

(Data Platform and Tools :: General, enhancement)

Product:
Data Platform and Tools
Component:
General
Platform:
x86_64
Other
Type:
enhancement
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED INVALID

People

(Reporter: amiyaguchi, Unassigned)

Details

There are two jobs schedule in w.t.m.o that are on an @weekly basis, churn and longitudinal. These jobs were not scheduled on March 12, 2017. One possibility is daylight savings losing an hour, and never hitting 00:00:00 on 2017-03-12. This only affected weekly jobs, since most of the daily jobs seem unaffected. Churn and longitudinal were manually scheduled (with job run suffixed with `_manual`) and executed on 2017-03-15, with start and end dates being set to 2017-03-12. It would be nice to clearly understand why the job failed and email the wider fx-data-platform once the data for churn and longitudinal are confirmed to be backfilled correctly.
This behavior was as expected, since DS_WEEKLY sets the start date 6 days into the future. The displayed date in airflow is behind the actual date, and would have been run on the 18th.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → INVALID
Component: Scheduling → General
You need to log in before you can comment on or make changes to this bug.