# NousResearch/hermes-agent · Weixin iLink prepare failure misclassified as rate limit

## Open now

- Nothing open on GitHub.

These items address a bug where Weixin iLink \`'prepare failed'\` errors are incorrectly treated as rate-limit violations, disrupting cron and notification delivery. Fixes focus on correcting the classification and retrying prepare failures without tripping the rate-limit circuit breaker.

## 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 #113069. Verify it addresses your case.
- **Recommended:** read PR #113069 (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-113069`. 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

- #112709: Weixin: iLink "prepare failed" misclassified as rate limit, breaking cron/notification delivery

## Prior & competing PRs

- **#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 · fix tier `verified`
  - maintainer direction: category `merged`
  - 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`
- **#112713: fix(gateway): retry Weixin prepare failures without token**. closed without merge
  - maintainer direction: category `silent_close`; implication `active`

## Fix status

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