Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix Bug: routed non-main Discord session remains processing,q=1 after run:completed, delaying typing

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…

Code Example

agent:george:discord:channel:1486566189055344710(processing,q=1,age=9s last=run:completed)

---

agent:george:whatsapp:group:...(idle,q=1,age=23213s last=run:completed)
RAW_BUFFERClick to expand / collapse

A Discord channel routed to a non-main agent remains marked active/processing after the run completes:

agent:george:discord:channel:1486566189055344710(processing,q=1,age=9s last=run:completed)

During that window, followup messages appear to queue before typing starts, producing a visible ~7-11s delay before Discord typing appears. The main-agent routed channel does not show the same delay.

Tried /stop in the affected channel, but it did not fully clear the queued/processing state. The same George Discord session still showed processing,q=1 after run:completed.

There is also an older stale queue item for another George session:

agent:george:whatsapp:group:...(idle,q=1,age=23213s last=run:completed)

Session stores are not large:

  • George ~862 KB / 36 sessions
  • Alex ~226 KB / 14 sessions
  • Main ~2.4 MB / 119 sessions

Expected:

After run:completed, the routed Discord session should clear active/processing state promptly, and /stop should clear queued/processing state for the target session.

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…
#tensor shape#autograd error#model save/load#optimization#mixed precision

Still need to ship something?

×6

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

Back to top recommendations

TRENDING

openclaw - 💡(How to fix) Fix Bug: routed non-main Discord session remains processing,q=1 after run:completed, delaying typing