You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by GitBox <gi...@apache.org> on 2022/10/13 17:25:54 UTC

[GitHub] [airflow] kcphila commented on issue #26991: Jobs scheduled with cron-syntax for monthly or weekly execution are not triggering

kcphila commented on issue #26991:
URL: https://github.com/apache/airflow/issues/26991#issuecomment-1277945251

   @ephraimbuddy, Aha! 
   
   I had the `start_date` set to ` datetime.datetime.now(tz=localtz) - datetime.timedelta(days=2)` and `catchup = False`.  I changed the start_date to a couple months ago and reset the crontab to run and it ran.
   
   I've generally not used the start_date for anything meaningful and we don't have tasks that should backfill, and so those were standard parameters (so standard that I have a separate constructor that sets the defaults if not explicitly set). Should I infer from this that the `start_date` must be some time before the last full interval that is being run? 
   
   Is there any utility to `start_date` except in conjunction with `catchup` in order to backfill iterative tasks? Would it be better to set the start date to, say, the start of epoch if it's not used to avoid issues like this, or would that have other side effects?


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

To unsubscribe, e-mail: commits-unsubscribe@airflow.apache.org

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