Skip to content

(schedules): never move the scheduler's last evaluated minute backwards (#1034) - #1036

Merged
devsuitup merged 2 commits into
mainfrom
wt/1034
Nov 9, 2026
Merged

devsuitup merged 2 commits into
mainfrom
wt/1034

Conversation

@devsuitup

Copy link
Copy Markdown
Owner

Closes #1034.

lastTickMinute now only moves forward. Without this, a resume check whose project list resolved after a newer tick could rewind it, and re-enabling a catch-up schedule would then replay that tick's minute. The regression goes through the real scheduler with a deferred resume.

No changelog entry: the Schedules tab (#1035) has not been released yet.

Harness-Claim: true
Agent: switchboard-dev
Host: ANCHOR
Base-Ref: origin/main
Base-SHA: 3aefedd
Claimed-At: 2026-11-09T00:07:49.3993961Z
Nonce: 51065caa16ef2636
A resume check whose project list resolves after a newer tick no longer rewinds the minute the re-enable skip relies on.
@devsuitup devsuitup added the no-changelog The PR changes nothing a user sees; the CHANGELOG.md check is waived label Nov 9, 2026
@devsuitup
devsuitup merged commit c171a90 into main Nov 9, 2026
6 checks passed
@devsuitup
devsuitup deleted the wt/1034 branch November 9, 2026 02:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

no-changelog The PR changes nothing a user sees; the CHANGELOG.md check is waived

Projects

None yet

Development

Successfully merging this pull request may close these issues.

(schedules): never move the scheduler's last evaluated minute backwards

1 participant