GitHub user enchant3dmango added a comment to the discussion: Criteria for a
DAG being marked as stale
A DAG is marked as stale when the scheduler determines it hasn’t been refreshed
within the configured interval, meaning the DAG file wasn’t re-parsed or the
heartbeat of the DagFileProcessor timed out.
Common causes:
1. Scheduler/parser didn’t process the file – maybe the file was
removed, renamed, or moved out of the dags folder.
2. Scheduler not keeping up – too many DAGs or slow parsing can
cause the scheduler to lag and mark old ones stale.
3. Errors in the DAG file – if parsing fails (syntax/import
errors), Airflow will eventually drop it from the DB and UI.
You can check the scheduler logs for messages — that’ll tell you exactly when
and why it happened.
GitHub link:
https://github.com/apache/airflow/discussions/57173#discussioncomment-14922705
----
This is an automatically sent email for [email protected].
To unsubscribe, please send an email to: [email protected]
