Nataneljpwd commented on issue #58717: URL: https://github.com/apache/airflow/issues/58717#issuecomment-5106779200
> We are also using 3.2.2. > > In our case the dags are being marked as stale while `seconds_since_parsed` is way below the STALE_DAG_THRESHOLD which seems to cause the dags to temporarily disappear / flick in UI. > > We use git bundle... > > > > Deactivated %s dags... > > We also have logs like that in the dag-processor. > > ``` > 2026-07-28T14:44:45.556890Z [info ] Deactivating Dag bla1. Its bundle dags-bundle is no longer active. [airflow.dag_processing.manager.DagFileProcessorManager] loc=manager.py:391 > 2026-07-28T14:44:45.557032Z [info ] Deactivating Dag bla2. Its bundle dags-bundle is no longer active. [airflow.dag_processing.manager.DagFileProcessorManager] loc=manager.py:391 > 2026-07-28T14:44:45.557165Z [info ] Deactivating Dag bla3. Its bundle dags-bundle is no longer active. [airflow.dag_processing.manager.DagFileProcessorManager] loc=manager.py:391 > ... > 2026-07-28T14:44:45.562526Z [info ] Deactivated 43 DAGs which are no longer present in file. [airflow.dag_processing.manager.DagFileProcessorManager] loc=manager.py:421 > ``` > > > What should we look at ? The logs don't seem to contain anything useful. That means that either the dag processor did not parse the dag file at all probably, because it did not find the file for some reason, how are you using the git bundle? how are you mounting (if at all) the dag code to the dag processor? What kind of file system are you using? (I.e NFS os similar or block storage ot local storage) How many parsing processes does the processor have? It seems like they arearked as stale and removed immediately because the dag processor did not parse them at all and probably thinks the files where removed, do you encounter any permission denied errors or file not found errors? -- 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]
