feat: soft_fail TriggerDagRunOperator #39173
Merged
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.
If I have a lot of TriggerDagRunOperator in failed stated ( where some failed before triggering the dag_run and some after ) for any reason ( airflow worker unclean stop .., zombie task ... )
then if I clear all of them , some will be running then success and others will directly fail because dag_run already exists and was correctly trigger
So it's painful to manage this operator at real scaling ( thousands of runs )
with this option we can clear the operator and it will not fail in case the dag_run was correctly trigger