Airflow: New DAG is not found by webserver
airflow, airflow-scheduler
Solution
This helped me...
pkill -9 -f "airflow scheduler"
pkill -9 -f "airflow webserver"
pkill -9 -f "gunicorn"
then restart the airflow scheduler and webserver.
Problem
In Airflow, how should I handle the error "This DAG isn't available in the webserver DagBag object. It shows up in this list because the scheduler marked it as active in the metadata database"? I've copied a new DAG to an Airflow server, and have tried: - unpausing it and refreshing it (basic operating procedure, given in this previous answer https://stackoverflow.com/a/42291683/160406) - restarting the webserver - restarting the scheduler - stopping the webserver and scheduler, resetting the database (`airflow resetdb`), then starting the webserver and scheduler again - running `airflow backfill` (suggested here Airflow "This DAG isnt available in the webserver DagBag object ") - running `airflow trigger_dag` The scheduler log shows it being processed and no errors occurring, I can interact with it and view it's state through the CLI, but it still does not appear in the web UI. Edit: the webserver and scheduler are running on the same machine with the same airflow.cfg. They're not running in Docker. They're run by Supervisor, which runs them both as the same user (airflow). The airflow user has read, write and execute permission on all of the dag files.