openclaw - 💡(How to fix) Fix Follow-up to #76828: still reproduces on 2026.5.18 + DM silent-drop [1 comments, 2 participants]

Follow-up to #76828: still reproduces on 2026.5.18, plus one DM silent-drop

I tried to add this as a comment on #76828, but that issue appears locked for new comments from my account. Posting here to preserve the data.

Original: #76828

Summary

On 2026.5.18, the same silent-delivery pattern still reproduces.

New detail: we now have one DM drop in addition to topic-thread drops.

• Prior reports: topic-thread focused
• New evidence (same day/session):
  • 1 topic-thread silent drop
  • 1 DM silent drop (agent:main:telegram:default:direct:<dm_id>)

This suggests the bug is not only :topic:<id> session-key shape.

Incident A (topic-thread)

08:25:35.816  [context-engine] deferred turn maintenance queued
              sessionKey=agent:main:telegram:group:<chat_id>:topic:6
              ... assistant text persisted
              ... NO [telegram] outbound send ok follows
...
08:30:54.580  inbound prod from user
...
08:32:34.164  [telegram] outbound send ok ... [ws] message.action

Incident B (DM, new surface)

09:11:56.651  [context-engine] deferred turn maintenance queued
              sessionKey=agent:main:telegram:default:direct:<dm_id>
              ... assistant text persisted
              ... NO [telegram] outbound send ok follows
09:12:27.760  inbound prod from user ("I didn't get your message")
09:12:48.671  [telegram] outbound send ok ... [ws] message.action

Same-session DM control window

In the same ~50 minute window, 11 DM turns had normal delivery signatures (outbound send ~2-9s before turn-maintenance). Exactly 1 had none.

Hypothesis update

Likely not only topic-key parsing. More consistent with intermittent natural-stream dispatch failure/race/flush miss where turn text persists but channel send is not emitted (and no hard error surfaces).

If maintainers prefer, I can provide a redacted longer log window.