Hi,

I was running a 1.7 release candidate and noticed that the DAG status for
some reason came out of sync with the database.  In order to resolve this I
upgraded to 1.7.1.3 and the same condition is occurring.  Is there a
configuration in the DB or the airflow.cfg that I should be aware of that
could be causing this?  I've restarted the webserver and scheduler many
times with no success.

Any insights appreciated.  Thanks.

dan

Reply via email to