I'm seeing unexpected behaviour with backfilling for a dag, using the airflow CLI. After running: #26258
Replies: 1 comment
-
Not enough information. You should try upgrading to latest verrsion. There were a number of errors fixed since your version related to backfil, and this is the easiest way to check it - because otherwise diagnosis, analysis logs would have to take a lot of time (and we help for free here). Once you upgrade, lease see if you see the same issue. Also - in order to help the investiation you could run a series if experiments to see if this is the only dag that has the problem, possibly running some example, simple dags for comparision and generally try to isolate the problem and see if there is someting in common with the DAG(s) having the same problem (but only after upgrade to latest version). Looking forward for results of your digging in. converting to a discussion in the meantime |
Beta Was this translation helpful? Give feedback.
-
Related issue: #23808
I'm seeing unexpected behaviour with backfilling for a dag, using the airflow CLI. After running:
gcloud composer environments run [company environment] --location [location] dags backfill -- --reset-dagruns -s 2022-05-05 -e 2022-05-18 minimal_skip
I observe that 2022-05-05 is complete on the Airflow UI, but the next time it is run, i see 2022-05-07, rather than 2022-05-06 as expected.
I'm using Airflow 2.1.4 + composer
Originally posted by @philipmargeotab in #23808
Beta Was this translation helpful? Give feedback.
All reactions