Skip to content

Conversation

@jeremystretch
Copy link
Member

Fixes: #20243

When determining the new scheduled time for a job with an interval, ensure that it is at least one minute into the future.

@jeremystretch jeremystretch requested review from a team and bctiemann and removed request for a team September 29, 2025 19:17
@jnovinger jnovinger self-requested a review September 30, 2025 15:41
jnovinger
jnovinger previously approved these changes Sep 30, 2025
Copy link
Member

@jnovinger jnovinger left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this solves the problem as stated and is more than reasonable. I did have a couple of questions, though.

Also, I think we should probably follow this up with a housekeeping issue to add a test that enforces the "subsequent runs of periodic jobs are always in the future" expectation.

@jnovinger jnovinger merged commit 9bc60a1 into main Sep 30, 2025
10 checks passed
@jnovinger jnovinger deleted the 20243-system-jobs-minimal-interval branch September 30, 2025 18:27
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Oct 31, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

SystemHousekeepingJob runs multiple times in direct succession when executions were missed

3 participants