eladkal commented on a change in pull request #22025:
URL: https://github.com/apache/airflow/pull/22025#discussion_r820246980
##########
File path: docs/apache-airflow/concepts/dags.rst
##########
@@ -745,3 +745,34 @@ the dependency graph.
The dependency detector is configurable, so you can implement your own logic
different than the defaults in
:class:`~airflow.serialization.serialized_objects.DependencyDetector`
+
+DAG pausing, deactivation and deletion
+--------------------------------------
+
+The DAGs have several states when it comes to being "not running". DAGs can be
paused, deactivated
+and finally all metadata for the ``DAG`` can be deleted.
+
+Dag can be paused via UI when it is present in the ``DAGS_FOLDER``, and
scheduler stored it in
+the database, but the user chose to disable it via the UI. The
``pause/unpause`` actions are available
+via UI and API. Paused ``DAG`` is not scheduled by the Scheduler, but you can
trigger them via UI for
+manual runs.
Review comment:
This is a bit confusing I think?
When we trigger a manual run from the UI it also automatically change the
paused DAG to ON so it can run. If it is left in Off the dag will not be
scheduled. I'm not sue if that is the same for triggering via API
--
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]
