hermes - 💡(How to fix) Fix iLink WeChat sendmessage rate limiting (ret=-2) with no built-in retry or backoff [1 pull requests]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…

Fix Action

Fixed

Code Example

Weixin send failed: iLink sendmessage rate limited: ret=-2 errcode=None errmsg=rate limited
RAW_BUFFERClick to expand / collapse

Problem

When sending messages via iLink/WeChat (send_message tool), the platform returns rate limit errors:

Weixin send failed: iLink sendmessage rate limited: ret=-2 errcode=None errmsg=rate limited

No automatic retry or backoff. In a busy session, rapid sends trigger the limit causing message loss.

Environment

  • Hermes Agent: v2026.4.30
  • Platform: iLink/WeChat
  • Deployment: Docker multi-agent

Expected Behavior

  1. Automatic retry with exponential backoff (like jittered_backoff for LLM calls)
  2. Or message queuing to respect platform limits
  3. Or configurable rate limiter (messages_per_second in config.yaml)

Related

  • #20983 LLM API rate limit fix
  • #20908 rate guard HERMES_HOME fix

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

hermes - 💡(How to fix) Fix iLink WeChat sendmessage rate limiting (ret=-2) with no built-in retry or backoff [1 pull requests]