# NousResearch/hermes-agent · Cron multiplex delivery uses wrong bot or adapter

## Open now

- 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.

## TL;DR

- 7 member(s): 0 open issue(s), 1 closed issue(s), 0 open PR(s), 1 merged PR(s), 5 PR(s) closed without merging.
- A fix was merged to main in PR #99375. Verify it addresses your case.
- **Recommended:** read PR #99375 (and any competing PRs below) before filing. Confirm the merged change covers your symptom.

## Maintainer resolution verdict

- Internal-tracker verdict over this cluster's issue members: `unresolved`. This is distinct from the fix status above. Weigh it yourself.

## How this cluster was grouped

- Link evidence (`STRUCTURAL_SPANNING`): every member is connected by structural evidence: shared changed files, or a closing/superseded reference.
- Pairwise link density `0.29`: the share of member 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.

## Closed / duplicate issues

- #83182: Cron delivery uses wrong bot/chat under multiplex (secret-scope reset before delivery + shared-adapter dict)

## Prior & competing PRs

- **#99375: fix(cron): profile jobs deliver via their own bot and cron status stops lying (#94862 #99028 #98790, salvage x6)**. merged to main · fix tier `verified`
  - maintainer direction: category `merged`; implication `superseded`
  - 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`
- **#83557: fix(cron): multiplex delivery uses owning profile's bot token and adapter (#83182)**. closed without merge
  - maintainer direction: category `implemented_elsewhere`; implication `superseded`; refs `07f6518b6d6`, `51e377d550f`, `a07370abd05`, `#99375`, `#73363`, `#83182`
- **#91795: fix(cron): deliver profile-store jobs with the owning profile's bot under multiplex**. closed without merge
  - maintainer direction: category `duplicate_of`; implication `duplicate`; refs `9eb832aad7`, `#99375`, `#73363`, `#92526`
- **#96536: fix(cron): route multiplex delivery through profile adapters**. closed without merge
  - maintainer direction: category `duplicate_of`; implication `duplicate`; refs `#95899`
- **#98156: fix(cron): deliver multiplex profile jobs from the owning profile's bot**. closed without merge
  - maintainer direction: category `partial_fix`; implication `needs_llm`; refs `9eb832aad7`, `d0b2415afb`, `#99375`, `#92526`, `#73363`
- **#100374: fix(cron): multiplex profile adapters routing for cron delivery**. closed without merge
  - maintainer direction: category `implemented_elsewhere`; implication `superseded`

## Fix status

- Merged to main in PR #99375 (cited above). No release data is tracked. Verify downstream.
- Fix last verified (merged) `2026-08-31`.
- Subsystem: `cron`