jeffolsi commented on issue #8649:
URL: https://github.com/apache/airflow/issues/8649#issuecomment-623064361
@BasPH
This is the DAG defintion:
```
with DAG(
dag_id=DAG_NAME,
default_args=default_args,
schedule_interval=timedelta(minutes=60),
max_active_runs=1,
catchup=False
) as dag:
```
This is an example for the execution times:
As you can this DAG is hourly by `timedelta(minutes=60)` but it's not the
same as specifying `@hourly` or `0 * * * * `. You can also see the gap in
times (marked in red) when Airflow was down. When it got up again it gave a
"new" timestamp to the execution_date.
I'm sure you can understand that there is no business logic behind the time
stamp of `XX:46:10.998426`
So as said before `timedelta(minutes=60)` **is not equivalent to** `@hourly`
or cron job experssion.
----------------------------------------------------------------
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:
[email protected]
