dsuhinin opened a new pull request, #75304:
URL: https://github.com/apache/airflow/pull/75304

    Backfill reprocessing currently works at whole-run granularity: `failed` 
and `completed` recreate the entire run, so re running just the failed tasks of 
a run — or running only tasks added in a newer Dag version — requires clearing 
runs manually. This was possible in Airflow 2.x via task-regex backfills and 
was lost in the 3.0 backfill redesign. This PR adds two task-level 
`ReprocessBehavior` values, built on the existing `dag.clear(only_failed=...)` 
/ `dag.clear(only_new=...)` primitives:                                         
                                                                                
                                               
                                                                                
                                                                                
                                                                                
                                                                               
     - **`failed_tasks`** — reprocesses failed runs like `failed`, but clears 
only the failed (and upstream-failed) task instances instead of the whole run.  
                                                                                
                                                                                
 
     - **`new_tasks`** — reprocesses completed/failed runs, running only tasks 
added in the latest Dag version; existing task instances are untouched and the 
run moves to the latest Dag version.
   
   <img width="925" height="840" alt="Screenshot 2026-10-21 at 13 37 01" 
src="https://github.com/user-attachments/assets/97a2cdd9-80f0-4ce4-86df-abdbd7ecc06a";
 />
   


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