DagRun scheduled after end_date

[dud225]

Hello

Environment

Please fill out any appropriate fields:

• Airflow version: v1.7.0
• Airflow components: webserver and scheduler with a postgres database and LocalExecutor
• Python Version: 2.7.9

Description of Issue

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 never used.

Is there any reason for this behaviour ?

Regards
dud

[bolkedebruin]

@dud225 Please use Apache Jira for this as requested. In addition the the line just above what you highlighted considers end_date so your analysis does not seem entirely correct.

Closing.