# NousResearch/hermes-agent · Cron job failure diagnostics and traceback visibility

## Open now

- Nothing open on GitHub.

These issues and PRs address the difficulty of diagnosing cron job runs with errors by adding traceback information to output documents and surfacing \`last_error\` in job listings. The work centers on making \`failed\` run details accessible rather than silently swallowed.

## TL;DR

- 4 member(s): 0 open issue(s), 1 closed issue(s), 0 open PR(s), 1 merged PR(s), 2 PR(s) closed without merging.
- A fix was merged to main in PR #104928. Verify it addresses your case.
- **Recommended:** read PR #104928 (and any competing PRs below) before filing. Confirm the merged change covers your symptom.

## Maintainer resolution verdict

- Internal-tracker verdict over this cluster's issue members: `resolved` · deciding PR(s): `pr-104928`. 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.

## Closed / duplicate issues

- #104538: Cronjob fails with RuntimeError: Connection error (no stack trace)

## Prior & competing PRs

- **#104928: fix(cron): failed runs show useful local diagnostics (#104538, salvage #104545)**. merged to main · fix tier `verified`
  - maintainer direction: category `merged`
  - files: `cron/scheduler.py`, `cron/scheduler_diagnostics.py`, `evals/cron_error_diagnostics.py`, `hermes_cli/cli_commands_mixin.py`, `tests/cron/test_run_error_diagnostics.py`, `tools/cronjob_job_args.py`, `website/docs/user-guide/features/cron.md`
- **#104545: fix(cron): make failed runs diagnosable — traceback in the output doc, last_error in job listings**. closed without merge
  - maintainer direction: category `implemented_elsewhere`; implication `superseded`; refs `e1a161538a`, `#104538`, `#104928`, `#104554`
- **#104554: fix(cron): persist the full traceback in a failed run's output doc (#104538)**. closed without merge
  - maintainer direction: category `implemented_elsewhere`; implication `superseded`; refs `e1a161538a`, `#104538`

## Fix status

- Merged to main in PR #104928 (cited above). No release data is tracked. Verify downstream.
- Fix last verified (merged) `2026-09-07`.