Cairn

HERMES_CRON_TIMEOUT invalid value fallback bug

NousResearch/hermes-agent · cluster 11319 · cron

Data as of

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

The short answer

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

A bug where an invalid HERMES_CRON_TIMEOUT environment variable raises a ValueError instead of falling back to a default value. Multiple fixes and the original bug report address defensive parsing and graceful fallback behavior for this cron timeout setting.

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.

  • #17515 fix(cron): fall back gracefully when HERMES_CRON_TIMEOUT is invalid

    merged to main

    files: cron/scheduler.py, scripts/release.py, tests/cron/test_cron_inactivity_timeout.py

4 PRs closed without merging

From the close comments: done elsewhere 2 · PR volume cleanup 1 · merged via another change 1

  • #11328 fix(cron): fall back on invalid timeout env · merged via another change → ec27f0a, #17515, #11319, #11365, #11375
  • #11365 fix(cron): fall back gracefully when HERMES_CRON_TIMEOUT is invalid · done elsewhere → 6d84237, #17515, #11319
  • #11375 Fix invalid HERMES_CRON_TIMEOUT fallback in cron jobs · done elsewhere
  • #11882 fix(cron): defensive parsing for HERMES_CRON_TIMEOUT env var · PR volume cleanup
Closed issues · 1
  • Closed#11319[Bug]: invalid HERMES_CRON_TIMEOUT makes run_job fail with ValueError instead of falling back
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.33: 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
Merged PRs
#17515
Closed issues
1
Attempts
4 PRs closed without merging
Fix link checked
29 Apr 2026

For your agent

The same facts, typed.

cluster/11319.json
cluster/11319.md