Skip to content

Document nextRun parameter on UpdateJob#2637

Merged
tylerkaraszewski merged 1 commit into
mainfrom
blimpich-documentUpdateJobNextRun
Jun 12, 2026
Merged

Document nextRun parameter on UpdateJob#2637
tylerkaraszewski merged 1 commit into
mainfrom
blimpich-documentUpdateJobNextRun

Conversation

@blimpich

Copy link
Copy Markdown
Contributor

Details

UpdateJob has accepted and applied a nextRun parameter since 2020 (commit 5987b1e3, "Allow to update nextRun in UpdateJob"), and an explicit nextRun takes priority over the schedule computed from repeat. The docs, however, only list jobID, data, repeat, and jobPriority — so the capability is invisible to anyone reading them. This adds nextRun to the public Jobs docs (docs/jobs.md, which renders to bedrockdb.com/jobs) and the plugin README (plugins/Jobs.md).

Surfaced during review of Auth#21635, where the missing doc led a reviewer to believe UpdateJob ignores nextRun.

Fixed Issues

N/A — docs-only fix, no tracking issue.

Tests

Docs-only change; no code or behavior is affected. UpdateJob's nextRun handling is already covered by test/tests/jobs/UpdateJobTest.cpp.


Internal Testing Reminder: when changing bedrock, please compile auth against your new changes

– written by Claude on Ben's behalf

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@tylerkaraszewski tylerkaraszewski merged commit ac255dc into main Jun 12, 2026
8 checks passed
@tylerkaraszewski tylerkaraszewski deleted the blimpich-documentUpdateJobNextRun branch June 12, 2026 22:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants