1 Answers
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!
answered 16 days ago
Relevant questions
Ec2 instance goes down every day
asked 4 months agoWhy is my EventBridge Rule silently failing every week?
Accepted Answerasked 7 months agod3.micro Postgres RDS resetting instance every day
asked a month agomwaa pipeline scheduling issue
asked 17 days agoMWAA 2.2.2 CLI Backfill skips a day
asked a month agoIs it possible to divide test suite to run tests in parallel?
Accepted Answerasked 4 months agoUnable to run a Python script using BashOperator
Accepted Answerasked a year agoaurora serverless restarts in every ~ 4 hours
asked 2 days agoError scheduling backup every ten minutes in AWS Backup
Accepted Answerasked a month agoDAG import errors are not disappearing in the UI even after resolving them
Accepted Answerasked a year ago
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.