You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "John Smodic (JIRA)" <ji...@apache.org> on 2019/07/24 17:19:00 UTC
[jira] [Updated] (AIRFLOW-5037) Execution Date is 24 hours behind
[ https://issues.apache.org/jira/browse/AIRFLOW-5037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
John Smodic updated AIRFLOW-5037:
---------------------------------
Description:
For a scheduled DAG that runs every day at "0 2 * * *", the execution date is always behind.
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. But even then, the DAG runs fine, it just references the wrong date.
was:
For a scheduled DAG that runs every day at "0 2 * * *", the execution date is always behind.
!image-2019-07-24-13-14-57-686.png!
!image-2019-07-24-13-14-42-063.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. But even then, the DAG runs fine, it just references the wrong date.
> 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
>
>
> For a scheduled DAG that runs every day at "0 2 * * *", the execution date is always behind.
>
>
> 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. But even then, the DAG runs fine, it just references the wrong date.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)