We can't do that, unfortunately. Airflow schedule the task based on the current state in the DB. If you would like to preserve the history one option would be to add instrumentation on airflow_local_settings.py
Regards, Ananth.P, On 5 February 2018 at 13:09, David Capwell <dcapw...@gmail.com> wrote: > When a production issue happens it's common that we clear the history to > get airflow to run the task again. This is problematic since it throws > away the history making finding out what real happened harder. > > Is there any way to rerun a task without deleting from the DB? >
