Hi, we sometimes have the situation that a DagRun is started, but it needs to be aborted. The current way of handling that situation is to stop airflow, reinitialize the database and restart airflow. Is there a better way how to handle this in the airflow UI without erasing the history of DagRuns?
Regards, Christian
