cedric-fauth commented on issue #35220: URL: https://github.com/apache/airflow/issues/35220#issuecomment-2160665825
> In our pipeline, we occasionally disable some DAGs to prevent them from executing. Another use case is during testing, based on the value of a variable, I decide which DAG should appear in the DAG list. It gets loaded but is inactive. I enable it and it triggers immediately, but since auto-refresh is not enabled, it's not apparent that it has been triggered and task processing has begun within it. Consequently, I hit play and then realize that it's already running. In this regard, I find such behavior to be non-intuitive for the user and hence consider it a bug. Hi, we have the same issue with airflow. I understand this is expected but it would be a great enhancement if there was a feature to turn off the immediate-run behavior when unpausing a dag with `catchup=False`. -- 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: commits-unsubscr...@airflow.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
