1 Risposta
- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
0
Hi!
A newly added DAG will generally run once, even with catchup=False, if there was a valid run time since start_date. To avoid this, set start date to the next run time you wish.
If there were failures and retries are enabled, that may account for the addition downstream executions. To confirm you can check your dag run history to see if there were any additional runs.
Cheers!
con risposta 2 anni fa
Contenuto pertinente
- AWS UFFICIALEAggiornata 2 anni fa
- AWS UFFICIALEAggiornata 8 mesi fa
- AWS UFFICIALEAggiornata un anno fa
- AWS UFFICIALEAggiornata 3 anni fa
hey, thank you for your response. this isn't a new DAG, it's an old DAG that had a cron schedule (0 0 1 */3 *) and I changed it to @quarterly, and just to make sure it aligned with all the other DAGS I changed the start date to -datetime(2022, 1, 1). is it possible that the dag runs without any documentation in the airflow UI? I attached a snippet that shows that no runs were executed even dough I know that it did run. *UPDATE- it seems that there is no place to add snippet.