Cairn
NousResearch/hermes-agent

Cron execution history retention limits and fairness

Cluster 93616 · 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 items address the fixed 1000-row cap on cron execution history, proposing to make the retention limit configurable and to distribute history retention fairly across jobs so high-frequency jobs cannot crowd out records from less active ones.

Open issues1

  • Issue#93616Cron execution history pruned to 1000 rows (~36h at high job volume) — make MAX_TERMINAL_EXECUTIONS configurable

Open PRs2

  • PR#93858feat(cron): make execution-ledger retention cap configurable (#93616)
  • PR#126610fix(cron): a chatty job no longer evicts quiet jobs' execution history (per-job floor, salvage #124830)

1 PR closed without merging

From the close comments: other 1

  • #98511 feat(cron): retain execution history fairly per job · other → bc1330e, 8f11de0, #93858
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/93616.json
cluster/93616.md