Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix Gateway blocks on agent responses while direct API calls work

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…

The OpenClaw gateway blocks indefinitely when processing agent message responses, even though direct API calls to the model provider (Mistral) work fine.

Root Cause

The OpenClaw gateway blocks indefinitely when processing agent message responses, even though direct API calls to the model provider (Mistral) work fine.

Fix Action

Workaround

Direct API calls to Telegram/Slack work fine. Only the gateway's agent processing path is blocked.

Code Example

[diagnostic] stalled session: sessionKey=agent:main:telegram:direct:* 
  state=processing age=600s 
  reason=active_work_without_progress 
  classification=stalled_agent_run
  activeWorkKind=embedded_run
  lastProgress=codex_app_server:notification:thread/tokenUsage/updated

[diagnostic] liveness warning: 
  eventLoopDelayP99Ms=63686.3 
  eventLoopUtilization=0.996
RAW_BUFFERClick to expand / collapse

Summary

The OpenClaw gateway blocks indefinitely when processing agent message responses, even though direct API calls to the model provider (Mistral) work fine.

Environment

  • OpenClaw version: 2026.5.12
  • Platform: macOS Darwin 21.6.0
  • Node: v22.22.0 (via nvm)

Symptoms

  1. Inbound messages are received (logged as [telegram] Inbound message)
  2. No sendMessage response is ever sent
  3. sessions.usage calls take 68+ seconds
  4. Event loop utilization reaches 99%+
  5. Sessions get stuck in processing/embedded_run state for 10+ minutes

Diagnosis

Tested each component independently:

ComponentStatusEvidence
Telegram Bot API✅ WorksDirect curl to sendMessage succeeds instantly
Mistral API✅ WorksDirect curl to chat/completions returns in <5s
OpenClaw Gateway❌ BlockedNo sendMessage after inbound, sessions stall

Attempted Fixes (all failed)

  1. Switched model from Codex (openai/gpt-5.4) to Mistral (mistral-large-latest)
  2. Switched to faster model (mistral-medium-latest)
  3. Multiple gateway restarts
  4. Session /reset command
  5. Re-authenticated Codex OAuth

Log Evidence

[diagnostic] stalled session: sessionKey=agent:main:telegram:direct:* 
  state=processing age=600s 
  reason=active_work_without_progress 
  classification=stalled_agent_run
  activeWorkKind=embedded_run
  lastProgress=codex_app_server:notification:thread/tokenUsage/updated

[diagnostic] liveness warning: 
  eventLoopDelayP99Ms=63686.3 
  eventLoopUtilization=0.996

Workaround

Direct API calls to Telegram/Slack work fine. Only the gateway's agent processing path is blocked.

Expected Behavior

Agent should respond to messages within reasonable time (<30s), not block indefinitely.

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…
#api#optimization#mixed precision#training loop#device allocation

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 Gateway blocks on agent responses while direct API calls work