kaxil commented on code in PR #73763: URL: https://github.com/apache/airflow/pull/73763#discussion_r4122883430
########## airflow-core/docs/core-concepts/dags.rst: ########## @@ -813,6 +815,16 @@ the scheduler automatically changes the Dag to paused. A backfill started while the drain until its Dag runs have been created and finished. While a Dag is draining, you can cancel the drain to make the Dag active again. +To execute a manual run, backfill or asset materialization on a paused Dag without resuming its schedule, Review Comment: Trying to be precise about my concern, since "paused" and "draining" are getting used interchangeably here. **Paused has to mean "nothing on this Dag starts", with no exceptions.** Today `is_paused` alone answers "can anything run on this Dag?". Once there is an exception, whether it comes from the trigger form or from an override flag on the run, every reader (the scheduler, the UI, API clients, a user scanning the Dags list) has to check "paused AND ...". I don't want that second check anywhere tbh. -- 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]
