NousResearch/hermes-agent
Cron catch-up: execute missed or skipped recurring jobs
Cluster 27327 · cron. Data as of
1 open item. Fix attempted, not merged.
The short answer
1open issue
0open PRs
4items grouped
- Known?
- Yes. 4 related items grouped here, 2 issues already closed.
- Fix event
- No fix has been merged to main. 1 PR closed without merging; see the attempts below.
- Tracker
- The maintainers' tracker marks this
unresolved. That is separate from the fix event. - Still open
- 1 issue and 0 PRs.
Next step: read the attempts below. Your case may extend or revive that work.
Pick up a Lab taskThese issues and PRs concern adding a 'catchup' option and related fixes to ensure missed or deferred recurring cron jobs are executed rather than silently skipped or perpetually deferred.
Open issues1
- Issue#51668[Feature]: 支持条件触发调度（on_available / catch-up 语义）
Open PRs0
1 PR closed without merging
From the close comments: superseded by another PR 1
-
#27333 feat(cron): add `catchup` option to execute missed recurring jobs (closes #27327) · superseded by another PR →
#33315,#33318,#27327
Closed issues · 2
How this cluster was grouped
-
Link evidence (
partly structural links): some members are connected by structural evidence (shared changed files, or a closing/superseded reference); the rest are joined by an automated relevance judgement over their text. - Members outside that structural core may belong to a different underlying problem.
-
Pairwise link density
0.29: 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 LabAt a glance
- Subsystem
- cron
- Closed issues
- 2
- Attempts
- 1 PR closed without merging