> 2) Many times, especially once a DAG is running, in the UI I see the warning
> "The scheduler does not appear to be running.”
The other thing that was an issue: `SCHEDULER_RUNS` in the environment was set
to some value `> -1`. This was causing "The scheduler does not appear to be
running.” wa
I just discovered, that Flower renders Tasks, as soon as I’m using a
`BranchPythonOperator`. So that does not appear to be a setup problem.
> On 6. May 2020, at 12:11, Andreas Balke wrote:
>
> Hi Ash,
>
> that appears to be OK:
>
> ● airflow-scheduler.service - Airflow scheduler daemon
>
Hi Ash,
that appears to be OK:
● airflow-scheduler.service - Airflow scheduler daemon
Loaded: loaded (/lib/systemd/system/airflow-scheduler.service; enabled;
vendor preset: enabled)
Active: active (running) since Wed 2020-05-06 10:09:20 UTC; 3s ago
Main PID: 10610 (/usr/bin/python)
Your second point there would lead me to believe that the scheduler is
still actually running with the default SequentialExecutor.
Which config file did you edit?
What output is shown when you (re)start the scheduler?
Thanks,
-ash
On May 6 2020, at 11:00 am, Andreas Balke wrote:
> Dear Airflo
