[ https://issues.apache.org/jira/browse/AIRFLOW-2639?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16618044#comment-16618044 ]
Stefan Seelmann commented on AIRFLOW-2639: ------------------------------------------ As https://github.com/apache/incubator-airflow/pull/3460 / https://issues.apache.org/jira/browse/AIRFLOW-2355 now is in 1.10 I suggest to not consider this change because it would change behaviour again. I closed https://github.com/apache/incubator-airflow/pull/3540. > Dagrun of subdags is set to RUNNING immediately > ----------------------------------------------- > > Key: AIRFLOW-2639 > URL: https://issues.apache.org/jira/browse/AIRFLOW-2639 > Project: Apache Airflow > Issue Type: Bug > Reporter: Chao-Han Tsai > Assignee: Chao-Han Tsai > Priority: Major > > This change has a side-effect. The subdag run and it's task instances are > eagerly created, the subdag is immediately set to "RUNNING" state. This means > it is immediately visible in the UI (tree view and dagrun view). > In our case we skip the SubDagOperator base on some conditions. However the > subdag run is then still visible in th UI and in "RUNNING" state which looks > scary, see attached screenshot. Before there was no subdag run visible at all > for skipped subdags. > One option I see is to not set subdags to "RUNNING" state but "NONE". Then it > will still be visible in the UI but not as running. Another idea is to try to > pass the conf directly in the SubDagOperator. -- This message was sent by Atlassian JIRA (v7.6.3#76005)