Cairn

Cron multiplex delivery uses wrong bot or adapter

NousResearch/hermes-agent · cluster 83182 · cron

Data as of

Nothing open on GitHub. Fix merged in #99375. Check it covers your case.

The short answer

0open issues
0open PRs
7items grouped
Known?
Yes. 7 related items grouped here, 1 issue already closed.
Fix event
A fix was merged to main in PR #99375. 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
Nothing open on GitHub.

These issues and PRs address a bug where cron job delivery under multiplex mode uses the incorrect bot token and adapter, apparently due to secret-scope or shared-adapter dictionary problems. Fixes aim to ensure jobs are delivered using the owning profile's bot and chat context.

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.

  • #99375 fix(cron): profile jobs deliver via their own bot and cron status stops lying (#94862 #99028 #98790, salvage x6)

    merged to main

    files: contributors/emails/[redacted:email], contributors/emails/[redacted:email], contributors/emails/[redacted:email], cron/scheduler.py, cron/scheduler_provider.py, gateway/run.py, hermes_cli/cron.py, hermes_cli/gateway.py, tests/cron/test_87033_cronjob_gateway_liveness.py, tests/cron/test_cron_home_target_profile_scope.py, tests/cron/test_cron_multiplex_profile_route_preflight.py, tests/cron/test_run_one_job.py, tests/cron/test_scheduler_provider.py, tests/cron/test_sessiondb_init_hang.py, tests/hermes_cli/test_cron_status_profile_isolation.py

5 PRs closed without merging

From the close comments: done elsewhere 2 · duplicate 2 · partial fix 1

  • #83557 fix(cron): multiplex delivery uses owning profile's bot token and adapter (#83182) · done elsewhere → 07f6518, 51e377d, a07370a, #99375, #73363, #83182
  • #91795 fix(cron): deliver profile-store jobs with the owning profile's bot under multiplex · duplicate → 9eb832a, #99375, #73363, #92526
  • #96536 fix(cron): route multiplex delivery through profile adapters · duplicate → #95899
  • #98156 fix(cron): deliver multiplex profile jobs from the owning profile's bot · partial fix → 9eb832a, d0b2415, #99375, #92526, #73363
  • #100374 fix(cron): multiplex profile adapters routing for cron delivery · done elsewhere
Closed issues · 1
  • Closed#83182Cron delivery uses wrong bot/chat under multiplex (secret-scope reset before delivery + shared-adapter dict)
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.29: 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
#99375
Closed issues
1
Attempts
5 PRs closed without merging
Fix link checked
31 Aug 2026

For your agent

The same facts, typed.

cluster/83182.json
cluster/83182.md