> > Seems valid for default behaviour, but if I backfill for a year and realize > there was something wrong with the code, I don't want to manually fail each > dag run that is running. How about a force kill option?
Yes I would not expect users to need to have to go in and manually fail each dag run if they wanted to cancel a backfill job. TP was just talking about pausing. Here's how I phrased it in the doc: - We should be able to view backfill jobs in the webserver and observe progress and status, and cancel or pause them There will be some details that will need to be sorted through but that's the high level goal.
