Cairn
NousResearch/hermes-agent

Cron jobs: support multiple schedules per job

Cluster 49711 · cron. Data as of

3 open items. Fix attempted, not merged.

The short answer

1open issue
2open PRs
4items grouped
Known?
Yes. 4 related items grouped here, 0 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 2 PRs.

These issues and PRs explore adding support for multiple schedules or cron expressions per job, with one unrelated fix for passing HTTP timeouts as timedeltas in MCP.

Open issues1

  • Issue#49711Allow cron job `schedule` to accept multiple schedules

Open PRs2

  • PR#44572feat(cron): support multiple cron expressions per job (multi_cron)
  • PR#49646fix(mcp): pass legacy HTTP timeouts as timedeltas (#49629)

1 PR closed without merging

From the close comments: duplicate 1

  • #49742 feat(cron): support multiple schedules per job · duplicate → #44572
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.50: 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
Closed issues
0
Attempts
1 PR closed without merging

For your agent

The same facts, typed.

cluster/49711.json
cluster/49711.md