Cairn

Cron rescheduling failure on croniter ImportError

NousResearch/hermes-agent · cluster 127182

Data as of

Nothing open on GitHub. Fix merged in #130526. 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 #130526. Check it covers your case. No release data is tracked.
Tracker
The maintainers' tracker marks this resolved, deciding PR #130526. That is separate from the fix event.
Still open
Nothing open on GitHub.

These items concern a bug where a transient ImportError from croniter causes cron jobs to silently stop rescheduling, and proposed fixes to re-probe or recover rather than latching into a broken state.

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.

  • #130526 fix(cron): recurring jobs resume after a transient croniter import failure (#127182, salvage #127195)

    merged to main

    files: cron/jobs.py, cron/scheduler.py, tests/cron/test_jobs.py

4 PRs closed without merging

From the close comments: merged via another change 3 · done elsewhere 1

  • #127195 fix(cron): re-probe croniter after a transient ImportError instead of latching · done elsewhere → #130526
  • #127202 fix(cron): recover from transient croniter import failures · merged via another change → 8a1efff, #130526
  • #127514 fix(P1): Bug: Cron jobs silently stop rescheduling when croniter import fails · merged via another change → 8a1efff, #127182, #130526
  • #129719 fix(cron): retry croniter import instead of latching failure (#127182) · merged via another change → 8a1efff, #127195, #130526
Closed issues · 1
  • Closed#127182Cron jobs silently stop rescheduling when croniter import fails: stays enabled, next_run_at unset, only a log WARNING (build keeps state=error, contradicts #16265)
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

Merged PRs
#130526
Closed issues
1
Attempts
4 PRs closed without merging
Fix link checked
1 Oct 2026

For your agent

The same facts, typed.

cluster/127182.json
cluster/127182.md