# NousResearch/hermes-agent · Messaging platform /retry with multiplex_profiles gateway handling

## Open now

- Nothing open on GitHub.

The members all concern /retry from messaging platforms on multi-profile (multiplex_profiles) gateways, including a bug report citing RuntimeStoreError(invalid_params) and related changes to the gateway's retry redispatch path. The titles do not by themselves confirm the cause or the outcome.

## TL;DR

- 3 member(s): 0 open issue(s), 1 closed issue(s), 0 open PR(s), 1 merged PR(s), 1 PR(s) closed without merging.
- A fix was merged to main in PR #139149. Verify it addresses your case.
- **Recommended:** read PR #139149 (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: `resolved` · deciding PR(s): `pr-139149`. 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.67`: 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

- #139040: \[Bug\]: /retry from a messaging platform fails with RuntimeStoreError(invalid_params) when multiplex_profiles is on

## Prior & competing PRs

- **#139149: /retry from messaging platforms works again on multi-profile gateways (#139040, salvage #139044)**. merged to main · fix tier `verified`
  - maintainer direction: category `merged`
  - files: `contributors/emails/8476250+drzxk@users.noreply.github.com`, `gateway/session_ingress_context.py`, `gateway/slash_commands_session.py`, `tests/gateway/test_retry_native_provenance.py`, `tests/scripts/test_source_build_env.py`
- **#139044: fix(gateway): re-enter the native callback for a messaging /retry redispatch**. closed without merge
  - maintainer direction: category `implemented_elsewhere`; implication `superseded`; refs `51abb25ce0`, `4118c3774aa`, `#139149`, `#139257`

## Fix status

- Merged to main in PR #139149 (cited above). No release data is tracked. Verify downstream.
- Fix last verified (merged) `2026-10-15`.