Nothing open on GitHub. Fix merged in #93615. Check it covers your case.
The short answer
- Known?
- Yes. 6 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #93615. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #93615. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These issues and pull requests address a bug where editing or triggering a consumed one-shot cron job would resurrect it but then silently delete it instead of firing. The fixes ensure that re-arming a one-shot job correctly resets its run budget so it executes as expected.
Open issues0
Open PRs0
Fixes on record
-
#93615 Consumed one-shot cron jobs refuse silent resurrection; explicit re-arm added (#93524, salvage #89649)
files:
cron/__init__.py,cron/jobs.py,hermes_cli/console_engine.py,hermes_cli/cron.py,hermes_cli/subcommands/cron.py,tests/cron/test_terminal_job_rearm.py -
#93674 Due-scan removal of a re-armed one-shot is no longer silent (#93524 follow-up)
files:
cron/jobs.py,tests/cron/test_oneshot_guard_warning.py
3 PRs closed without merging
From the close comments: superseded by another PR 3
-
#93543 fix(cron): reset a consumed one-shot's quota when a schedule edit re-arms it · superseded by another PR →
a0ca7c1,#93524,#89649,#93615,#93674 -
#93585 fix(cron): editing or triggering a consumed one-shot must give it a fresh run budget · superseded by another PR →
a0ca7c1,#93524,#89649,#93615,#93674 -
#93641 fix(cron): rescheduled one-shot jobs fire again instead of being silently deleted (#93524, salvage #93543 + #93585) · superseded by another PR →
a0ca7c1,#93524,#89649,#93615,#93674
Closed issues · 1
- Closed#93524[Bug]: Editing a consumed one-shot's schedule resurrects it, then the scheduler silently deletes it instead of firing
How this cluster was grouped
-
Link evidence (
structural links throughout): every member is connected by structural evidence: shared changed files, or a closing/superseded reference. -
Pairwise link density
0.33: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36.1.00means every pair is linked.
Pick up a Lab task
Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.
Open the Lab