jieyao-MilestoneHub opened a new pull request, #44422:
URL: https://github.com/apache/airflow/pull/44422

   This PR handle missing DAGs when clearing task instances to prevent 
failures. When we delete DAG files and attempt to trigger them again, the 
process should access the DAGs and display an error indicating that the DAGs no 
longer exist, rather than causing the frontend to show an "Oops" error.
   
   ### Summary of Changes:
   - Added warning logs for missing DAGs to prevent silent failures during task 
clearing.
   - Improved error handling for downstream task clearing, including checks for 
partial_subset errors to handle cases where DAGs or downstream dependencies are 
unavailable.
   - Updated the docstring for _clear_task_instances for better clarity and 
consistent style.
   - Refined the grouping and handling of Task Instances by DAG and DAG Run to 
improve robustness and maintainability.
   
   
   ### Issue Reference:
   Closes https://github.com/apache/airflow/issues/44274
   
   ^ Add meaningful description above
   Read the [Pull Request 
Guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#pull-request-guidelines)
 for more information.
   In case of fundamental code changes, an Airflow Improvement Proposal 
([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvement+Proposals))
 is needed.
   In case of a new dependency, check compliance with the [ASF 3rd Party 
License Policy](https://www.apache.org/legal/resolved.html#category-x).
   In case of backwards incompatible changes please leave a note in a 
newsfragment file, named {pr_number}.significant.rst or 
{issue_number}.significant.rst, in 
[newsfragments](https://github.com/apache/airflow/tree/main/newsfragments).


-- 
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]

Reply via email to