Cairn
NousResearch/hermes-agent

One-shot cron jobs firing late after downtime

Cluster 93526. Data as of

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

The short answer

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

These issues and pull requests address a bug where stored past-due one-shot cron jobs bypass the ONESHOT_GRACE_SECONDS grace period and fire arbitrarily late after downtime instead of being retired as stale.

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.

  • #93558 One-shot cron jobs no longer fire hours late after downtime (#93526, salvage #89571)

    merged to main

    files: cron/jobs.py, cron/scheduler_provider.py, tests/cron/test_misfire_backstop_oneshot_grace.py, tests/cron/test_oneshot_grace_due_scan.py

3 PRs closed without merging

From the close comments: merged via another change 3

  • #93554 fix(cron): stop stale one-shot reminders after downtime · merged via another change → ed8ee9a, #93558, #89571
  • #93555 fix(cron): retire stale past-due one-shots instead of firing hours late · merged via another change → ed8ee9a, #93558, #89571
  • #93595 fix(cron): honor ONESHOT_GRACE_SECONDS for stored past-due one-shots (no more hours-late fires) · merged via another change → ed8ee9a, #93558, #89571
Closed issues · 1
  • Closed#93526[Bug]: Stored past-due one-shot jobs bypass ONESHOT_GRACE_SECONDS and fire arbitrarily late after downtime
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.40: 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
#93558
Closed issues
1
Attempts
3 PRs closed without merging
Fix link checked
24 Aug 2026

For your agent

The same facts, typed.

cluster/93526.json
cluster/93526.md