Conversation
…h sub-threshold ticks.
github-actions
bot
added
the
Scope: Backend
wedamija
approved these changes
Jan 21, 2026
Abdkhan14
deleted the
abdk/crons-detector-schedule-preview-status-smearing
branch
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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
…h sub-threshold ticks.
At large thresholds, the bucket interval exceeds the interval of the schedule being previewed. So we group multiple ticks into the same bucket. A bucket therefore can contain multiple statuses.
We don't want this in the UI, makes the issue open period boundaries less intuitive. This should only show the sub-threshold
status: