Make start_date optional for @continuous schedule #61405
+23
−8
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
When start_date is not specified, continuous DAGs will begin running immediately when unpaused, using the current time as the starting point. Previously if you didn't have a start date (the default in 3.0) it would do nothing when it was unpaused. This aligns with Airflow 3.0's philosophy of making start_date optional for schedules that don't require historical backfilling.
Member
Author
|
We could choose to put this in 3.1 as a bugfix, but I think it's better in 3.2 so people have more of a chance of reasing the news fragment just in case. |
vincbeck
approved these changes
Feb 3, 2026
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When
start_dateis not specified, continuous DAGs will now begin runningimmediately when unpaused, using the current time as the starting point.
Previously if you didn't have a start date (the default in 3.0) it would do
nothing when it was unpaused.
This aligns with Airflow 3.0's philosophy of making start_date optional
for schedules that don't require historical backfilling.