NousResearch/hermes-agent

Cron job failure diagnostics and traceback visibility

Cluster 104538. Data as of 2026-10-24 04:06 UTC

Nothing open on GitHub. Fix merged in #104928 on 7 Sep 2026. Check it covers your case.

open issues

open PRs

items grouped

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

Next step: read #104928, then check it covers your case.

Read #104928 Pick up a Lab task

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.

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.

#104928 fix(cron): failed runs show useful local diagnostics (#104538, salvage #104545)

merged to main

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

2 PRs closed without merging

From the close comments: done elsewhere 2

#104545 fix(cron): make failed runs diagnosable — traceback in the output doc, last_error in job listings · done elsewhere → e1a1615, #104538, #104928, #104554
#104554 fix(cron): persist the full traceback in a failed run's output doc (#104538) · done elsewhere → e1a1615, #104538

Closed issues · 1

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

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

Merged PRs: #104928
Closed issues: 1
Attempts: 2 PRs closed without merging
Fix link checked: 7 Sep 2026

For your agent

The same facts, typed.

cluster/104538.json
cluster/104538.md