[
https://issues.apache.org/jira/browse/AIRFLOW-39?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Siddharth Anand reassigned AIRFLOW-39:
--------------------------------------
Assignee: Siddharth Anand
> DagRun scheduled after end_date
> -------------------------------
>
> Key: AIRFLOW-39
> URL: https://issues.apache.org/jira/browse/AIRFLOW-39
> Project: Apache Airflow
> Issue Type: Wish
> Environment: - Airflow version: v1.7.0
> - Airflow components: webserver and scheduler with a postgres database and
> LocalExecutor
> - Python Version: 2.7.9
> Reporter: dud
> Assignee: Siddharth Anand
> Priority: Minor
>
> Hello
> When I write a new DAG, it is automatically picked by the scheduler as
> intended. However the end_date parameter is not accounted when creating a
> DagRun, so that DagRuns scheduled after end_date are being displayed in the
> web interface and are staying in the running state forever as the scheduler
> doesn't launch them.
> From my reading of the sources, the end_date paremeter is not used when
> creating a DagRun.
> Is there any reason for this behaviour ?
> Regards
> dud
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
