GitHub user DixT-180 deleted a comment on the discussion: ERROR - DagFileProcessorManager (PID=1234 last sent a heartbeat 50.42 seconds ago! Restarting it
The place where I worked had this exact issue: the Airflow UI wasn't reflecting DAG changes. DAGs that had been updated or removed weren't being reflected, and the UI appeared to be stuck showing the state from several days earlier. The issue was resolved by clearing the Airflow metadata database — either by truncating the relevant DAG-related metadata tables or, as a more drastic option, dropping and recreating the entire Airflow metadata database. After recreating the database, the Airflow schema had to be initialized/migrated again before starting the scheduler and webserver. GitHub link: https://github.com/apache/airflow/discussions/19270#discussioncomment-17985582 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
