Repository navigation
simplify(automation): admit concrete schedules before due decisions - #4551
Open
ScriptedAlchemy wants to merge 1 commit into
Open
ScriptedAlchemy wants to merge 1 commit into
ScriptedAlchemy wants to merge 1 commit into
Conversation
|
ScriptedAlchemy
force-pushed
the
simplify/automation-resolved-schedule
branch
from
October 26, 2026 05:48
4d634db to
45fedda
Compare
ScriptedAlchemy
force-pushed
the
simplify/automation-resolved-schedule
branch
from
October 26, 2026 07:15
45fedda to
0374d13
Compare
This branch has not been deployed
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 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.
Why
Refs #4428. Parent link is #4542 on
simplify/automation-task-lease.Fixed tasks and jobs interpreted the same schedule string and interval during validation and each due decision. Resolve that pair at admission so decisions cannot reconstruct conflicting timing states.
What changed
Arc.ConfiguredInterval, the old parser/validator APIs, repeated decision parsing and invalid-to-manual fallbacks.Scope
Blast Radius
Scheduled fixed tasks, host receipts, user jobs and scheduler status use the admitted timing representation. Retry, activity, denial, cancellation and retained settlement behavior stay covered. Three retry fixtures now use a valid one-second cooldown and wait for that boundary instead of bypassing settings with zero.
Verification