[jira] [Commented] (AIRFLOW-1156) Using a timedelta object as a Schedule Interval with catchup=False causes the start_date to no longer be honored.

[ https://issues.apache.org/jira/browse/AIRFLOW-1156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16430007#comment-16430007 ] John Cheng commented on AIRFLOW-1156: - Same problem with version 1.9 {code:java}

[jira] [Commented] (AIRFLOW-1156) Using a timedelta object as a Schedule Interval with catchup=False causes the start_date to no longer be honored.

[ https://issues.apache.org/jira/browse/AIRFLOW-1156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16425378#comment-16425378 ] Antti Ruokomäki commented on AIRFLOW-1156: -- Additionally, this seems to occur with a regular

[jira] [Commented] (AIRFLOW-1156) Using a timedelta object as a Schedule Interval with catchup=False causes the start_date to no longer be honored.

[ https://issues.apache.org/jira/browse/AIRFLOW-1156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16425366#comment-16425366 ] Antti Ruokomäki commented on AIRFLOW-1156: -- I've noticed similar behavior, when schedule is

[jira] [Commented] (AIRFLOW-1156) Using a timedelta object as a Schedule Interval with catchup=False causes the start_date to no longer be honored.

[ https://issues.apache.org/jira/browse/AIRFLOW-1156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16331533#comment-16331533 ] André da Silva Pinto commented on AIRFLOW-1156: --- This also causes the initial run to