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 18:14:00 UTC

[jira] [Closed] (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 closed AIRFLOW-5037.
--------------------------------
    Resolution: Not A Problem

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