NousResearch/hermes-agent

Weixin iLink stale session misclassification fix

Cluster 96416. Data as of 2026-10-30 11:57 UTC

Nothing open on GitHub. Fix merged in #113069 on 16 Sep 2026. Check it covers your case.

open issues

open PRs

items grouped

Known?: Yes. 3 related items grouped here, 1 issue already closed.
Fix event: A fix was merged to main in PR #113069. 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.

Next step: read #113069, then check it covers your case.

Read #113069 Pick up a Lab task

These items concern a bug where stale iLink session errors are incorrectly classified as rate-limit violations, causing misleading 'cooldown active' errors that block Weixin cron and notification delivery. The work focuses on correctly distinguishing session errors from rate-limit conditions in the gateway.

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.

#113069 fix(gateway): Weixin cron/notification sends recover from iLink 'prepare failed' instead of tripping the rate-limit breaker (#112709, salvage #112713)

merged to main

files: gateway/platforms/weixin.py, tests/gateway/test_weixin.py, website/docs/user-guide/messaging/weixin.md, website/i18n/zh-Hans/docusaurus-plugin-content-docs/current/user-guide/messaging/weixin.md

1 PR closed without merging

From the close comments: done elsewhere 1

#96437 fix(gateway): classify iLink stale sessions correctly · done elsewhere → 46ab37c, 5db9f02, #113069, #112713, #80152, #80156

Closed issues · 1

Closed#96416Weixin (iLink) adapter misclassifies stale session (-14/-2) as rate limit; misleading 'cooldown active' error blocks cron delivery

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

Merged PRs: #113069
Closed issues: 1
Attempts: 1 PR closed without merging
Fix link checked: 16 Sep 2026

For your agent

The same facts, typed.

cluster/96416.json
cluster/96416.md