# NousResearch/hermes-agent · Cleaner error handling for corrupted cron jobs.json

## Open now

- 1 issue, 2 PRs open on GitHub.
- #136723: \[Bug\]: hermes cron dumps a traceback when jobs.json is unparseable
- PR #136765: fix(cron): report corrupted store errors cleanly
- PR #136824: fix(cron): surface a corrupt jobs.json as one error line, not a traceback

These members concern \`hermes cron\` showing a traceback when \`jobs.json\` is corrupted or unparseable. One is a bug report and the others are fix proposals aiming to report the problem as a clean, single-line error. The titles do not indicate whether any change has been merged or verified.

## TL;DR

- 4 member(s): 1 open issue(s), 0 closed issue(s), 2 open PR(s), 0 merged PR(s), 1 PR(s) closed without merging.
- No fix has been merged to main; one or more PRs were attempted (see below).
- **Recommended:** review the prior/competing PR(s) below. A fix was attempted but not merged; your case may extend or revive that work.

## Maintainer resolution verdict

- Internal-tracker verdict over this cluster's issue members: `unresolved`. This is distinct from the fix status above. Weigh it yourself.

## How this cluster was grouped

- Link evidence (`STRUCTURAL_SPANNING`): every member is connected by structural evidence: shared changed files, or a closing/superseded reference.
- Pairwise link density `0.50`: the share of member 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.

## Open related issues

- #136723: \[Bug\]: hermes cron dumps a traceback when jobs.json is unparseable

## Prior & competing PRs

- **#136765: fix(cron): report corrupted store errors cleanly**. open
  - maintainer direction: category `implemented_elsewhere`; implication `superseded`; refs `37cc3ea2089`, `c0ef5af5205dbdc25e9e44acd66873b4bb3503c9`
  - files: `cron/jobs.py`, `hermes_cli/cron.py`, `tests/cron/test_cron_store_errors.py`, `tests/hermes_cli/test_cron.py`
- **#136824: fix(cron): surface a corrupt jobs.json as one error line, not a traceback**. open
  - maintainer direction: category `silent_close`; implication `active`
  - files: `hermes_cli/cron.py`, `tests/hermes_cli/test_cron_corrupt_store_cli.py`
- **#136862: fix(cli): fail hermes cron cleanly on a corrupted jobs.json**. closed without merge
  - maintainer direction: category `uncategorized`; implication `needs_llm`

## Fix status

- No merged fix on record.
- Subsystem: `hermes_cli`