Cron job parsing resilience for malformed entries

NousResearch/hermes-agent · cluster 123281

Data as of

Nothing open on GitHub. Fix merged in #124034. Check it covers your case.

The short answer

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

These issues and fixes address cases where invalid or malformed entries in jobs.json—such as non-object items or bad repeat counters—cause all cron jobs to stop firing. The changes aim to make the cron system skip or normalize bad data rather than halting entirely.

Open issues0

No open issues.

Open PRs0

No open pull requests.

Fixes on record

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

  • #124034 fix(cron): keep firing when jobs.json has junk entries or a null repeat counter (salvage #123285)

    merged to main

    files: contributors/emails/[redacted:email], cron/jobs.py, tests/cron/test_jobs.py, website/docs/user-guide/features/cron.md, website/i18n/zh-Hans/docusaurus-plugin-content-docs/current/user-guide/features/cron.md

  • #124111 fix(cron): an Infinity or negative repeat.completed no longer breaks load_jobs

    merged to main

    files: cron/jobs.py, tests/cron/test_jobs.py, website/docs/user-guide/features/cron.md, website/i18n/zh-Hans/docusaurus-plugin-content-docs/current/user-guide/features/cron.md

2 PRs closed without merging

From the close comments: done elsewhere 2

  • #123285 fix(cron): skip non-object entries in jobs.json instead of halting every tick · done elsewhere → 06a495c, f077152, #124034, #124111
  • #123405 fix(cron): normalize malformed jobs at the store boundary · done elsewhere → 06a495c, f077152, #124034, #124111
Closed issues · 1
  • Closed#123281[Bug]: a single non-object entry in cron/jobs.json stops every cron job from 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.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

Merged PRs
#124034, #124111
Closed issues
1
Attempts
2 PRs closed without merging
Fix link checked
26 Sep 2026

For your agent

The same facts, typed.