vdolez-happn commented on issue #9327: URL: https://github.com/apache/airflow/issues/9327#issuecomment-1401749941
Here a future DAG_run represents a DAG_run with an execution_date not yet reached by the scheduler (i.e now < execution_date + dag_period) Here's a *Use Case* for this feature : A have a Sensor on a DAG which waits for an file. I know that I won't receive that file tomorrow, and I want to ignore the sensor status for tomorrow's run. I can backfill and mark_success the sensor, but this will create a DAG run for tomorrow which will be either `running` / `failed` / `success`. I don't want the DAG run to be in a finished state, but I don't want it to be running yet. What I did then is I deleted the DAG run using the UI, and the DAG run successfully the following day. **As an** Airflow user, **I want to** change the state of a task in a DAG_run which will be trigger in the future by the scheduler without impacting other tasks scheduled for this specific DAG_run **In order to** anticipate task_instance state and manually by-pass domain rules -- 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]
