[
https://issues.apache.org/jira/browse/AIRFLOW-5037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16892056#comment-16892056
]
jack commented on AIRFLOW-5037:
-------------------------------
On the 24/07/19 at 02:00 the "DAG of" 23/07/19 02:00 become runable.
This is what you see. It's not behind.
If you expect exeution_date=24/07/19 02:00 to run on 24/07/19 02:00 then you
are confusing airflow execution_date with something you might know from other
systems. The name can be misleading!
[https://airflow.apache.org/scheduler.html#scheduling-triggers]
"
Note that if you run a DAG on a {{schedule_interval}} of one day, the run
stamped {{2016-01-01}} will be trigger soon after {{2016-01-01T23:59}}. In
other words, the job instance is started once the period it covers has ended.
*Let’s Repeat That* The scheduler runs your job one {{schedule_interval}} AFTER
the start date, at the END of the period."
> Execution Date is 24 hours behind
> ---------------------------------
>
> Key: AIRFLOW-5037
> URL: https://issues.apache.org/jira/browse/AIRFLOW-5037
> Project: Apache Airflow
> Issue Type: Bug
> Components: webserver
> Affects Versions: 1.10.2
> Reporter: John Smodic
> Priority: Minor
> Attachments: Selection_999(022).png, airflow.png
>
>
> For a scheduled DAG that runs every day at "0 2 * * *", the execution date as
> displayed is always behind.
>
> !Selection_999(022).png!
> !airflow.png!
> The tooltip doesn't seem to match (but it does for manually triggered DAGs),
> and even then it's showing a date that's already passed. The DAG runs fine,
> it just references the wrong date after the fact.
>
> The config is set to UTC and this is deployed in aws on separate webserver /
> scheduler nodes.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
