[GitHub] [airflow] kaxil commented 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>]

kaxil commented on issue #14969:
URL: https://github.com/apache/airflow/issues/14969#issuecomment-805414231


   I don't think it is a bug. When you use `schedule_interval=timedelta(minutes=5)` it just tell scheduler to run every 5 minutes. Now when `catchup=False`, it tells scheduler to run first as soon as it can and then every 5 mins from then onwards.
   
   This is the main difference between Cron vs Timedelta. While Cron does not take account of "last time", timedetla is dependent on the "last time". For example Cron `0 1 * * *` just says perform an action everyday at 1 am.


-- 
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