adds catch_up configuration option
#48
Merged
Conversation
This file contains 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 a cluster hasn't run for a while, the default behavior is to keep executing schedules until they are caught up with the present time. By setting `catch_up` to False, schedules will not play catch up and instead get rescheduled to the future.
Koed00
added a commit
that referenced
this pull request
Aug 18, 2015
adds `catch_up` configuration option
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 a cluster hasn't run for a while, the default behavior is to keep executing schedules until they are caught up with the present time.
By setting
catch_upto False, schedules will not play catch up and instead get rescheduled to the future.