Cairn
NousResearch/hermes-agent

Cron run history leaks across prefix-overlapping jobs

Cluster 92133 · cron. Data as of

2 open items. Fix merged in #139273 on 15 Oct 2026. Check it covers your case.

The short answer

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

A bug causes cron job run history to bleed into sibling jobs when one job ID is an underscore-prefix of another. The members include the bug report and two fix attempts addressing this prefix-overlap issue.

Open issues1

  • Issue#92133[Bug]: cron run history leaks runs across jobs when one job id is an underscore-prefix of another

Open PRs1

  • PR#92141fix(cron): keep prefixed jobs out of each other run history

Fixes on record

Merged to main. A stamp counts the issues a fix is linked to.

  • #139273 fix(cron): find unified-runtime cron runs by their scheduler admission

    merged to main

    files: apps/desktop/src/app/chat/sidebar/cron-jobs-section.tsx, apps/desktop/src/app/cron/index.tsx, apps/desktop/src/app/cron/open-cron-run.test.ts, apps/desktop/src/app/cron/open-cron-run.ts, apps/desktop/src/app/session/hooks/use-prompt-actions/submit.ts, gateway/session_cron.py, hermes_cli/web_routers/cron.py, hermes_cli/web_routers/sessions.py, hermes_state_common.py, hermes_state_keys.py, hermes_state_media.py, hermes_state_portability.py, tests/fakes/cron_owner.py, tests/hermes_cli/test_cron_run_history_sessions.py, tests/hermes_state/test_cron_run_sessions.py, tests/hermes_state/test_hermes_state.py

2 PRs closed without merging

From the close comments: done elsewhere 1 · superseded by another PR 1

  • #92158 fix(cron): stop run-history leaking a sibling job's runs on prefix overlap · superseded by another PR → e2042c8, 5894e75
  • #138968 fix(cron): find unified-runtime cron runs by their scheduler admission · done elsewhere → #139273, #139268
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

Subsystem
cron
Merged PRs
#139273
Closed issues
0
Attempts
2 PRs closed without merging
Fix link checked
15 Oct 2026

For your agent

The same facts, typed.

cluster/92133.json
cluster/92133.md