NousResearch/hermes-agent

Cron manual run cancels next scheduled occurrence

Cluster 105690 · cron. Data as of 2026-10-27 11:58 UTC

1 open item. Fix merged in #106306 on 9 Sep 2026. Check it covers your case.

open issues

open PR

items grouped

Known?: Yes. 5 related items grouped here, 1 issue already closed.
Fix event: A fix was merged to main in PR #106306. Check it covers your case. No release data is tracked.
Tracker: The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open: 0 issues and 1 PR.

Next step: read #106306, then check it covers your case.

Read #106306 Pick up a Lab task

These issues and pull requests concern a bug where triggering a cron job manually off its scheduled tick incorrectly stamps or overwrites the next scheduled occurrence, causing it to be silently cancelled. Multiple fixes and approaches to preserving the next occurrence after a manual run are represented.

Open issues0

No open issues.

Open PRs1

PR#105956fix(cron): require explicit manual run marker

Fixes on record

Merged to main. A stamp counts the issues a fix is linked to.

#106306 fix(cron): an off-tick "run now" no longer cancels the job's next scheduled run (#104790, #105690, #106166; salvage #105704)

merged to main

files: contributors/emails/[email protected], cron/jobs.py, cron/scheduler_provider.py, hermes_cli/web_server_cron.py, tests/cron/test_claim_job_for_fire.py, tests/cron/test_scheduler_provider.py, tests/hermes_cli/test_web_server_cron_profiles.py, tests/tools/test_cronjob_run_background.py, tests/tools/test_cronjob_run_immediate.py, tools/cronjob_tools.py

2 PRs closed without merging

From the close comments: done elsewhere 1 · superseded by another PR 1

#105704 fix(cron): don't stamp the next occurrence on an off-tick manual run · done elsewhere → a73b750, #106306
#105939 fix(cron): preserve next occurrence after manual run · superseded by another PR → #105948

Closed issues · 1

Closed#105690cron: an off-tick manual run stamps the NEXT scheduled occurrence and silently cancels it

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.40: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36. 1.00 means 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

At a glance

Subsystem: cron
Merged PRs: #106306
Closed issues: 1
Attempts: 2 PRs closed without merging
Fix link checked: 9 Sep 2026

For your agent

The same facts, typed.

cluster/105690.json
cluster/105690.md