Cairn

QQ Bot expired reply msg_id fallback handling

NousResearch/hermes-agent · cluster 43467 · gateway

Data as of

4 open items. Fix attempted, not merged.

The short answer

1open issue
3open PRs
5items grouped
Known?
Yes. 5 related items grouped here, 0 issues already closed.
Fix event
No fix has been merged to main. 1 PR closed without merging; see the attempts below.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
1 issue and 3 PRs.

These issues and PRs address a scenario where QQ Bot loses group message responses when the reply msg_id has expired, implementing a fallback to standalone message sending in that case.

Open issues1

  • Issue#43467QQ Bot: group message response lost when agent takes >msg_id expiry window — retry loop on expired msg_id

Open PRs3

  • PR#43480fix(qqbot): fall back to standalone send when reply msg_id expires
  • PR#85221fix(qqbot): fall back to standalone message on expired reply
  • PR#134416fix(gateway): forward event_message_id as reply_to in background task completion delivery

1 PR closed without merging

From the close comments: superseded by another PR 1

  • #43594 fix(qqbot): fallback to standalone msg on expired msg_id (#43467) · superseded by another PR → #43480, #43467
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.40: 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

Subsystem
gateway
Closed issues
0
Attempts
1 PR closed without merging

For your agent

The same facts, typed.

cluster/43467.json
cluster/43467.md