Adding retry logic to peer DM transient failures
Cluster 115325. Data as of
Nothing open on GitHub. Fix merged in #116964 on 20 Sep 2026. Check it covers your case.
The short answer
- Known?
- Yes. 4 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #116964. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #116964. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These items address a missing retry policy in the peer DM transport, which unlike local and relayed DM lanes did not retry on transient turn failures. Changes span the peer, API server, and gateway layers.
Open issues0
Open PRs0
Fixes on record
-
#116964 fix(peer): hermes peer dm retries a transient turn once and hides a bare silence marker (#115325, salvage #115380 #111992)
files:
agent/session_persistence.py,gateway/platforms/api_server.py,hermes_cli/quiet_single_query.py,hermes_cli/subcommands/peer.py,tests/gateway/test_peer_dm_transient_retry.py,tests/hermes_cli/test_peer_cmd.py,tools/bot_failure_reasons.py
2 PRs closed without merging
From the close comments: done elsewhere 1 · merged via another change 1
Closed issues · 1
- Closed#115325hermes peer dm never retries a transient turn failure — the third DM transport is missing the retry policy local and relayed DMs share (#93091 item 5)
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.67: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36.1.00means 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 LabAt a glance
- Merged PRs
- #116964
- Closed issues
- 1
- Attempts
- 2 PRs closed without merging
- Fix link checked
- 20 Sep 2026