Cairn
NousResearch/hermes-agent

Cron delivery falsely confirmed without positive evidence

Cluster 77763 · cron. Data as of

Nothing open on GitHub. Fix merged in #100908 on 2 Sep 2026. Check it covers your case.

The short answer

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

A bug caused cron agent jobs to log messages as delivered even when no actual delivery occurred, particularly with empty payloads. The fixes require positive evidence before confirming delivery, so empty or failed deliveries are no longer reported as successful.

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.

  • #100908 fix(cron): live-adapter delivery is confirmed by positive evidence, empty payloads fail closed, cron pushes notify (#77763, salvage #100284 #58262)

    merged to main

    files: cron/jobs.py, cron/scheduler.py, gateway/delivery.py, hermes_cli/config_defaults.py, hermes_cli/cron.py, tests/cron/test_cron_live_delivery_confirmation.py, tests/gateway/test_delivery_silence_filter.py, tests/hermes_cli/test_cron.py, tools/cronjob_tools.py, website/docs/user-guide/features/cron.md

2 PRs closed without merging

From the close comments: merged via another change 1 · superseded by another PR 1

  • #77792 fix(cron): do not report empty delivery as delivered (#77763) · superseded by another PR → 00a7115, #100908, #100284, #77763
  • #100284 fix(cron): require positive evidence for live-adapter delivery confirmation · merged via another change → 00a7115, #100908
Closed issues · 1
  • Closed#77763# [Bug] Cron agent job logs "delivered" but message never sent to Telegram
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
#100908
Closed issues
1
Attempts
2 PRs closed without merging
Fix link checked
2 Sep 2026

For your agent

The same facts, typed.

cluster/77763.json
cluster/77763.md