[6.x] Dispatch event when a scheduled command was filtered from running #30407
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
If a scheduled command is run with a truth constraint, it is not simple to check whether the task didn't run at all, or if it was filtered running from a known system constraint. Firing an event when the task is intentionally skipped allows monitoring over the task executing as scheduled, based on the truth constraint.
michaeldyrynda
changed the title
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.
If a scheduled command is run with a truth constraint, it is not simple to check whether the task didn't run at all, or if it was filtered running from a known system constraint.
Firing an event when the task is intentionally skipped allows monitoring over the task executing as scheduled, based on the truth constraint.