feat: set BEAT_CRON_STARTING_DEADLINE #8876
Merged
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
rudimatz
approved these changes
May 1, 2025
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #8876 +/- ##
=======================================
Coverage 88.79% 88.79%
=======================================
Files 314 314
Lines 41401 41402 +1
=======================================
+ Hits 36763 36764 +1
Misses 4638 4638 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
This configures beat to look back at most 30 minutes (1800 seconds) when deciding if a PeriodicTask scheduled via a crontab schedule is due. The value was chosen to be long enough that tasks missed by a moderately problematic production deployment will still run, but that we won't be surprised by a task running at entirely the wrong time.
This will not impact newly created tasks, only ones that have a "last run" time that's too long ago.
https://docs.celeryq.dev/en/main/userguide/configuration.html#beat-cron-starting-deadline