Gateway background completion notifications on Discord and Telegram retry behavior
NousResearch/hermes-agent · cluster 138940 · gateway
Data as of
Nothing open on GitHub. Fix merged in #139026. Check it covers your case.
The short answer
- Known?
- Yes. 5 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #139026. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #139026. That is separate from the fix event. - Still open
- Nothing open on GitHub.
The members concern background process or job completion notifications in the gateway, mainly for Discord and Telegram, including reports of delivery problems and repeated retry or requeue behavior. Related items touch on bounding retries and admitting completion wakes whose source differs only by message_id; the titles alone do not establish outcomes.
Open issues0
Open PRs0
Fixes on record
-
#139026 fix(gateway): Discord/Telegram background completions reach the agent instead of requeueing forever (#138940, salvage #138947 #138967 #138986)
files:
contributors/emails/[redacted:email],gateway/platforms/base.py,gateway/run_notifications.py,gateway/session_automation.py,tests/gateway/test_automation_notification_category.py,tests/gateway/test_background_process_notifications.py,tests/gateway/test_internal_wake_reply_anchor.py
3 PRs closed without merging
From the close comments: done elsewhere 2 · superseded by another PR 1
-
#138947 fix(gateway): bound failed completion notification retries · done elsewhere →
2bc1edb,#139026 -
#138967 fix(gateway): admit completion wakes whose source differs only by message_id · done elsewhere →
2bc1edb,#139026 -
#139032 Background-job completions reach the chat again on Telegram and Discord (#138940, salvage #138967) · superseded by another PR →
2bc1edb,#139026,#138940,#138967,#138986,#138947
Closed issues · 1
- Closed#138940[Bug]: Background process completion notifications fail delivery to Discord and spin in infinite retry injection loop
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.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
- Subsystem
- gateway
- Merged PRs
- #139026
- Closed issues
- 1
- Attempts
- 3 PRs closed without merging
- Fix link checked
- 15 Oct 2026