NousResearch/hermes-agent

Cron scheduled runs breaking due to stale module caches

Cluster 98976. Data as of 2026-10-30 11:57 UTC

Nothing open on GitHub. Fix merged in #99521 on 31 Aug 2026. Check it covers your case.

open issues

open PRs

items grouped

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

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

Read #99521 Pick up a Lab task

These items concern in-process scheduled cron jobs failing with ImportError after extended uptime, apparently caused by stale sys.modules entries. The group includes a bug report and two related fix attempts addressing module cache isolation for scheduled runs.

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.

#99521 fix(cron): isolate lazy imports from stale module caches (salvage #98996)

merged to main

files: agent/agent_init.py, agent/agent_runtime_helpers.py, agent/auxiliary_client.py, agent/codex_headers.py, cron/scheduler.py, gateway/platforms/base.py, plugins/image_gen/openai-codex/__init__.py, run_agent.py, tests/cron/test_stale_module_leaf_imports.py, tools/environments/base.py, tools/environments/docker.py, tools/environments/path_utils.py, tools/environments/singularity.py

1 PR closed without merging

From the close comments: done elsewhere 1

#98996 fix(cron): keep scheduled runs working with stale module caches · done elsewhere → #99521

Closed issues · 1

Closed#98976Scheduled in-process cron fires fail with ImportError ('cannot import name X') after hours of uptime — stale sys.modules; manual lane unaffected

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 1.00: 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: #99521
Closed issues: 1
Attempts: 1 PR closed without merging
Fix link checked: 31 Aug 2026

For your agent

The same facts, typed.

cluster/98976.json
cluster/98976.md