Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

first run after turning on will be the latest scheduled run #45768

Open
1 task done
Arjit-Sharma001 opened this issue Jan 17, 2025 · 3 comments
Open
1 task done

first run after turning on will be the latest scheduled run #45768

Arjit-Sharma001 opened this issue Jan 17, 2025 · 3 comments
Labels
kind:feature Feature Requests kind:meta High-level information important to the community

Comments

@Arjit-Sharma001
Copy link

Body

Description
Currently, catchup=False means "first run after turning on will be the latest scheduled run" and there is no way to produce the behavior where turning on a DAG means "make the first run after turning on occur at the next schedule time instead of the previous one".

Proposal: make a new flag (call it something to the effect of no_catchup_means_no_past_runs) which when set to True means that turning on a DAG that has the setting catchup=False will result in the first run being the one on the schedule that occurs next in time (rather than the one that occurs in the most recent past).

Use case/motivation
The use case is whenever you want to turn on a DAG without it running right away.

Committer

  • I acknowledge that I am a maintainer/committer of the Apache Airflow project.
@Arjit-Sharma001 Arjit-Sharma001 added the kind:meta High-level information important to the community label Jan 17, 2025
Copy link

boring-cyborg bot commented Jan 17, 2025

Thanks for opening your first issue here! Be sure to follow the issue template! If you are willing to raise PR to address this issue please do so, no need to wait for approval.

@dosubot dosubot bot added the kind:feature Feature Requests label Jan 17, 2025
@potiuk
Copy link
Member

potiuk commented Jan 18, 2025

Are you really committer? Should you use new feature request for that one?

@potiuk
Copy link
Member

potiuk commented Jan 18, 2025

I doubt we want to add even more complexity and new flag. You can attempt to make a PR to add that and see how complex it would be - I guess pretty complex, but what you should do is to set start_date properly on your DAG when you create it - to start at the date you want it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind:feature Feature Requests kind:meta High-level information important to the community
Projects
None yet
Development

No branches or pull requests

2 participants