-
Notifications
You must be signed in to change notification settings - Fork 16.3k
Fix DAG disappearing after callback execution in stale detection #55698
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
2 tasks
2 tasks
jedcunningham
approved these changes
Sep 16, 2025
When `min_file_process_interval` exceeds `stale_dag_threshold`, DAGs would incorrectly disappear after callback processing. This occurred because callback-only processing updated file processing timestamps but not DAG parsing timestamps, causing stale DAG detection to trigger false positives. The fix prevents callback-only processing from updating `last_finish_time`, ensuring DAGs remain active when only callbacks are executed. fixes apache#55315
d542ef7 to
326c7f9
Compare
kaxil
added a commit
that referenced
this pull request
Sep 16, 2025
) When `min_file_process_interval` exceeds `stale_dag_threshold`, DAGs would incorrectly disappear after callback processing. This occurred because callback-only processing updated file processing timestamps but not DAG parsing timestamps, causing stale DAG detection to trigger false positives. The fix prevents callback-only processing from updating `last_finish_time`, ensuring DAGs remain active when only callbacks are executed. fixes #55315 (cherry picked from commit 98e2f6a)
suman-himanshu
pushed a commit
to suman-himanshu/airflow
that referenced
this pull request
Sep 17, 2025
…che#55698) When `min_file_process_interval` exceeds `stale_dag_threshold`, DAGs would incorrectly disappear after callback processing. This occurred because callback-only processing updated file processing timestamps but not DAG parsing timestamps, causing stale DAG detection to trigger false positives. The fix prevents callback-only processing from updating `last_finish_time`, ensuring DAGs remain active when only callbacks are executed. fixes apache#55315
abdulrahman305 bot
pushed a commit
to abdulrahman305/airflow
that referenced
this pull request
Sep 30, 2025
…che#55698) When `min_file_process_interval` exceeds `stale_dag_threshold`, DAGs would incorrectly disappear after callback processing. This occurred because callback-only processing updated file processing timestamps but not DAG parsing timestamps, causing stale DAG detection to trigger false positives. The fix prevents callback-only processing from updating `last_finish_time`, ensuring DAGs remain active when only callbacks are executed. fixes apache#55315
abdulrahman305 bot
pushed a commit
to abdulrahman305/airflow
that referenced
this pull request
Oct 1, 2025
…che#55698) When `min_file_process_interval` exceeds `stale_dag_threshold`, DAGs would incorrectly disappear after callback processing. This occurred because callback-only processing updated file processing timestamps but not DAG parsing timestamps, causing stale DAG detection to trigger false positives. The fix prevents callback-only processing from updating `last_finish_time`, ensuring DAGs remain active when only callbacks are executed. fixes apache#55315
abdulrahman305 bot
pushed a commit
to abdulrahman305/airflow
that referenced
this pull request
Oct 2, 2025
…che#55698) When `min_file_process_interval` exceeds `stale_dag_threshold`, DAGs would incorrectly disappear after callback processing. This occurred because callback-only processing updated file processing timestamps but not DAG parsing timestamps, causing stale DAG detection to trigger false positives. The fix prevents callback-only processing from updating `last_finish_time`, ensuring DAGs remain active when only callbacks are executed. fixes apache#55315
abdulrahman305 bot
pushed a commit
to abdulrahman305/airflow
that referenced
this pull request
Oct 3, 2025
…che#55698) When `min_file_process_interval` exceeds `stale_dag_threshold`, DAGs would incorrectly disappear after callback processing. This occurred because callback-only processing updated file processing timestamps but not DAG parsing timestamps, causing stale DAG detection to trigger false positives. The fix prevents callback-only processing from updating `last_finish_time`, ensuring DAGs remain active when only callbacks are executed. fixes apache#55315
abdulrahman305 bot
pushed a commit
to abdulrahman305/airflow
that referenced
this pull request
Oct 4, 2025
…che#55698) When `min_file_process_interval` exceeds `stale_dag_threshold`, DAGs would incorrectly disappear after callback processing. This occurred because callback-only processing updated file processing timestamps but not DAG parsing timestamps, causing stale DAG detection to trigger false positives. The fix prevents callback-only processing from updating `last_finish_time`, ensuring DAGs remain active when only callbacks are executed. fixes apache#55315
abdulrahman305 bot
pushed a commit
to abdulrahman305/airflow
that referenced
this pull request
Oct 5, 2025
…che#55698) When `min_file_process_interval` exceeds `stale_dag_threshold`, DAGs would incorrectly disappear after callback processing. This occurred because callback-only processing updated file processing timestamps but not DAG parsing timestamps, causing stale DAG detection to trigger false positives. The fix prevents callback-only processing from updating `last_finish_time`, ensuring DAGs remain active when only callbacks are executed. fixes apache#55315
abdulrahman305 bot
pushed a commit
to abdulrahman305/airflow
that referenced
this pull request
Oct 5, 2025
…che#55698) When `min_file_process_interval` exceeds `stale_dag_threshold`, DAGs would incorrectly disappear after callback processing. This occurred because callback-only processing updated file processing timestamps but not DAG parsing timestamps, causing stale DAG detection to trigger false positives. The fix prevents callback-only processing from updating `last_finish_time`, ensuring DAGs remain active when only callbacks are executed. fixes apache#55315
abdulrahman305 bot
pushed a commit
to abdulrahman305/airflow
that referenced
this pull request
Oct 7, 2025
…che#55698) When `min_file_process_interval` exceeds `stale_dag_threshold`, DAGs would incorrectly disappear after callback processing. This occurred because callback-only processing updated file processing timestamps but not DAG parsing timestamps, causing stale DAG detection to trigger false positives. The fix prevents callback-only processing from updating `last_finish_time`, ensuring DAGs remain active when only callbacks are executed. fixes apache#55315
abdulrahman305 bot
pushed a commit
to abdulrahman305/airflow
that referenced
this pull request
Oct 8, 2025
…che#55698) When `min_file_process_interval` exceeds `stale_dag_threshold`, DAGs would incorrectly disappear after callback processing. This occurred because callback-only processing updated file processing timestamps but not DAG parsing timestamps, causing stale DAG detection to trigger false positives. The fix prevents callback-only processing from updating `last_finish_time`, ensuring DAGs remain active when only callbacks are executed. fixes apache#55315
abdulrahman305 bot
pushed a commit
to abdulrahman305/airflow
that referenced
this pull request
Oct 9, 2025
…che#55698) When `min_file_process_interval` exceeds `stale_dag_threshold`, DAGs would incorrectly disappear after callback processing. This occurred because callback-only processing updated file processing timestamps but not DAG parsing timestamps, causing stale DAG detection to trigger false positives. The fix prevents callback-only processing from updating `last_finish_time`, ensuring DAGs remain active when only callbacks are executed. fixes apache#55315
abdulrahman305 bot
pushed a commit
to abdulrahman305/airflow
that referenced
this pull request
Oct 10, 2025
…che#55698) When `min_file_process_interval` exceeds `stale_dag_threshold`, DAGs would incorrectly disappear after callback processing. This occurred because callback-only processing updated file processing timestamps but not DAG parsing timestamps, causing stale DAG detection to trigger false positives. The fix prevents callback-only processing from updating `last_finish_time`, ensuring DAGs remain active when only callbacks are executed. fixes apache#55315
abdulrahman305 bot
pushed a commit
to abdulrahman305/airflow
that referenced
this pull request
Oct 11, 2025
…che#55698) When `min_file_process_interval` exceeds `stale_dag_threshold`, DAGs would incorrectly disappear after callback processing. This occurred because callback-only processing updated file processing timestamps but not DAG parsing timestamps, causing stale DAG detection to trigger false positives. The fix prevents callback-only processing from updating `last_finish_time`, ensuring DAGs remain active when only callbacks are executed. fixes apache#55315
abdulrahman305 bot
pushed a commit
to abdulrahman305/airflow
that referenced
this pull request
Oct 12, 2025
…che#55698) When `min_file_process_interval` exceeds `stale_dag_threshold`, DAGs would incorrectly disappear after callback processing. This occurred because callback-only processing updated file processing timestamps but not DAG parsing timestamps, causing stale DAG detection to trigger false positives. The fix prevents callback-only processing from updating `last_finish_time`, ensuring DAGs remain active when only callbacks are executed. fixes apache#55315
abdulrahman305 bot
pushed a commit
to abdulrahman305/airflow
that referenced
this pull request
Oct 14, 2025
…che#55698) When `min_file_process_interval` exceeds `stale_dag_threshold`, DAGs would incorrectly disappear after callback processing. This occurred because callback-only processing updated file processing timestamps but not DAG parsing timestamps, causing stale DAG detection to trigger false positives. The fix prevents callback-only processing from updating `last_finish_time`, ensuring DAGs remain active when only callbacks are executed. fixes apache#55315
abdulrahman305 bot
pushed a commit
to abdulrahman305/airflow
that referenced
this pull request
Oct 15, 2025
…che#55698) When `min_file_process_interval` exceeds `stale_dag_threshold`, DAGs would incorrectly disappear after callback processing. This occurred because callback-only processing updated file processing timestamps but not DAG parsing timestamps, causing stale DAG detection to trigger false positives. The fix prevents callback-only processing from updating `last_finish_time`, ensuring DAGs remain active when only callbacks are executed. fixes apache#55315
abdulrahman305 bot
pushed a commit
to abdulrahman305/airflow
that referenced
this pull request
Oct 17, 2025
…che#55698) When `min_file_process_interval` exceeds `stale_dag_threshold`, DAGs would incorrectly disappear after callback processing. This occurred because callback-only processing updated file processing timestamps but not DAG parsing timestamps, causing stale DAG detection to trigger false positives. The fix prevents callback-only processing from updating `last_finish_time`, ensuring DAGs remain active when only callbacks are executed. fixes apache#55315
abdulrahman305 bot
pushed a commit
to abdulrahman305/airflow
that referenced
this pull request
Oct 19, 2025
…che#55698) When `min_file_process_interval` exceeds `stale_dag_threshold`, DAGs would incorrectly disappear after callback processing. This occurred because callback-only processing updated file processing timestamps but not DAG parsing timestamps, causing stale DAG detection to trigger false positives. The fix prevents callback-only processing from updating `last_finish_time`, ensuring DAGs remain active when only callbacks are executed. fixes apache#55315
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When
min_file_process_intervalexceedsstale_dag_threshold, DAGs would incorrectly disappear after callback processing. This occurred because callback-only processing updated file processing timestamps but not DAG parsing timestamps, causing stale DAG detection to trigger false positives.The fix prevents callback-only processing from updating
last_finish_time, ensuring DAGs remain active when only callbacks are executed.fixes #55315
^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named
{pr_number}.significant.rstor{issue_number}.significant.rst, in airflow-core/newsfragments.