You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "Pavan Maguluri (Jira)" <ji...@apache.org> on 2020/01/07 19:25:00 UTC

[jira] [Created] (AIRFLOW-6500) dependency 'Execution Date' FAILED: Execution date is in the future

Pavan Maguluri created AIRFLOW-6500:
---------------------------------------

             Summary: dependency 'Execution Date' FAILED: Execution date is in the future
                 Key: AIRFLOW-6500
                 URL: https://issues.apache.org/jira/browse/AIRFLOW-6500
             Project: Apache Airflow
          Issue Type: Bug
          Components: DAG, scheduler
    Affects Versions: 1.10.6
            Reporter: Pavan Maguluri


I have the below Dag with "schedule_interval" set to None and "start_date" set to airflow.utils.dates.days_ago(1). 

Task1 --> Task2 --> End

When I triggered the Dag from the Web-UI it is failing with the below reason. Other Dags which has "schedule_interval" set to some value don't have this issue.

*[2020-01-07 07:06:39,962] \{taskinstance.py:624} INFO - Dependencies not met for <TaskInstance: pipeline.Task1 2020-01-07T07:06:58.550778+00:00 [queued]>, dependency 'Execution Date' FAILED: Execution date 2020-01-07T07:06:58.550778+00:00 is in the future (the current date is 2020-01-07T07:06:39.962619+00:00).*

 

Default Pipeline Arguments: 
{code:python}
PIPELINE_DEFAULT_ARGS = {
 'owner': 'owner',
 'start_date': airflow.utils.dates.days_ago(1),
 'depends_on_past': True,
 'email_on_failure': False,
 'email_on_retry': False,
}{code}
All the solutions that I have read online tags with schedule_interval set to some value and start_date being dynamic (like datetime.now()). I don't have either of those settings, but, still see the problem. 

Appreciate if you can shed some light to fix this issue.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)