karenbraganz commented on issue #44652: URL: https://github.com/apache/airflow/issues/44652#issuecomment-3113810448
I wonder if this is happening because the DAGs are not getting processed frequently enough and becoming stale once they exceed the [dag_stale_not_seen_duration](https://airflow.apache.org/docs/apache-airflow/2.10.3/configurations-ref.html#dag-stale-not-seen-duration). The `dag_stale_not_seen_duration` config is unique to a standalone DAG processor, which is why you may be not be seeing this issue when the DAG processor is part of the scheduler. Please search for the keyword "stales" in the scheduler logs. If the scheduler detects stale DAGs it will emit logs like "Found n stales dags not parsed after..." coming from [this line of code](https://github.com/apache/airflow/blob/c99887ec11ce3e1a43f2794fcf36d27555140f00/airflow/jobs/scheduler_job_runner.py#L2064C24-L2064C63). -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
