[GitHub] [airflow] KayleMaster edited a comment on issue #14969: Using a timedelta object as a Schedule Interval with catchup=False causes the start_date to no longer be honored

[GitBox <gi...@apache.org>]

KayleMaster edited a comment on issue #14969:
URL: https://github.com/apache/airflow/issues/14969#issuecomment-809131273


   I just encountered this issue at work today. It turns out I cannot write a DAG that runs every 6 hours from 11:30. I tried with cron `0 */6 * * *` but of course that runs 00:00/06:00 etc (that's expected behaviour). I switched to the obvious start_date + timedelta combo. But it turns out it just uses the DAG unpause time as the new start_date??? 
   Now I have to go around and do stupid things like writing schedules like `30 11,17,23,5 * * *` instead of just writing `timedelta(hours=6)`  
   For an application which is basically a glorified scheduler, Airflow seems it's not even doing a good job in that place too.
   ![image](https://user-images.githubusercontent.com/19154414/112800465-5b780680-9078-11eb-86bd-e543feb42bb2.png)
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org