shahar1 commented on issue #61344: URL: https://github.com/apache/airflow/issues/61344#issuecomment-4045821743
> <img width="733" height="449" alt="Image" src="https://github.com/user-attachments/assets/9e974dda-2a7f-478f-867a-fe640a5d7bfa"; /> > > @shahar1 @rahulmansharamani14 I have a technical question regarding DAG logic. Today is March 12, 2026, and I just added a new Operator named test1 to an existing DAG. > > I want to backfill/run only this specific Operator for the historical period of March 1, 2026, to March 11, 2026. However, I cannot find a button to trigger this at the Operator level. In the Grid/Graph view, the 'squares' for this new task are empty for those past dates and are not clickable. > > As a result, I am forced to backfill the entire DAG for those days, which is very inefficient. Am I missing something in the UI, or is there a better way to trigger a single task for a historical range without re-running everything? > > > To add: I have read the article you sent, but I still don't understand it very well. > AFAIK, Airflow does not provide an option to retrospectively run a single task for historical dates if that task did not exist in the original Dag run. While it is now possible to run the current version of a Dag for past logical dates, tasks in Airflow are always executed within the context of a Dag run. Running a task independently for past dates would mean executing it without the full Dag context, including the dependencies and structure that defined that run. Since changes to the Dag (such as adding tasks or modifying dependencies) effectively change that context, executing a single task retrospectively without recreating the corresponding Dag runs would not reflect the correct workflow state. For that reason, the typical approach is to trigger or backfill the Dag for the relevant dates rather than running an individual task in isolation. -- 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]
