Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix [Bug]: [WSL2] Global 30-min gateway stall (:29/:59) affects Telegram + Control UI [1 comments, 1 participants]

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…
GitHub stats
openclaw/openclaw#61616•Fetched 2026-04-08 02:56:46
View on GitHub
Comments
1
Participants
1
Timeline
2
Reactions
0
Author
alexandrey128-cellalexandrey128-cell
Participants
alexandrey128-cellalexandrey128-cell
Timeline (top)
commented ×1labeled ×1

Gateway stalls for ~2–3 minutes at exact half-hour boundaries (:29-:32 and :59-:02). During stall, Telegram and Control UI both become unresponsive.

Root Cause

Gateway stalls for ~2–3 minutes at exact half-hour boundaries (:29-:32 and :59-:02). During stall, Telegram and Control UI both become unresponsive.

RAW_BUFFERClick to expand / collapse

Bug type

Regression (worked before, now fails)

Beta release blocker

No

Summary

Summary

Gateway stalls for ~2–3 minutes at exact half-hour boundaries (:29-:32 and :59-:02). During stall, Telegram and Control UI both become unresponsive.

Environment

  • OpenClaw: 2026.4.2 (d74a122)
  • OS: WSL2 Ubuntu 24.04
  • Node: 22.22.1
  • Model setup: anthropic/claude-opus-4-6 main, local llama fallback

Symptoms

  • Control UI messages briefly appear then disappear / no processing- Telegram timeouts or delayed responses
  • Gateway health endpoint often still reports OK during stall

What I already tried

  • Disabled heartbeat / changed heartbeat cadence
  • Verified cron jobs are empty
  • Reinstalled OpenClaw
  • Disabled custom helper services (sentinel/dashboard/fake-ollama/llama)
  • Rebooted host
  • Issue still reproduces on this machine

Timing pattern

  • Reproducible since April 3
  • Clock-precise windows around :29/:59 every hour

Steps to reproduce

nothing just wait for the time

Expected behavior

this happened starting around April 3rd midnight when i was trying to figure out how to get gemma 4 working on my system and i also updated my openclaw same time cause i realized it was on a old version of it.

Actual behavior

not supposed to freeze and stall.

OpenClaw version

Current newest version

Operating system

Windows 11

Install method

No response

Model

Anthropic Opus

Provider / routing chain

Provider / routing chain: Inbound: Telegram bot + Control UI Gateway runtime: OpenClaw on WSL2 Ubuntu 24.04 Agent routing: main agent (default) Model routing: primary Anthropic, fallback local llama-server (OpenAI-compatible localhost endpoint) Outbound: Telegram + Control UI Note: fake-ollama shim service existed previously on localhost:11434 and was disabled during troubleshooting.

Additional provider/model setup details

No response

Logs, screenshots, and evidence

Impact and severity

stalls for 3-5 mins every 30 mins at around :28-:32 and :58-:02 at every hour and sometimes longer depending on what it was doing at the time. Been dealing with this for days and its a nightmare especially for what my agents are made for.

Additional information

No response

extent analysis

TL;DR

Investigate and adjust the scheduling or timing-related configurations in OpenClaw or its dependencies to prevent gateway stalls at half-hour boundaries.

Guidance

  • Review the OpenClaw configuration and dependencies for any scheduling or cron jobs that may be triggering at half-hour boundaries, despite the user verifying cron jobs are empty.
  • Investigate potential issues with the Node.js environment, such as scheduling or timing-related bugs, given the specific Node version (22.22.1) in use.
  • Consider temporarily disabling the Anthropics Opus model or the local llama fallback to isolate if the issue is model-specific.
  • Check for any hidden or overridden configuration files that may be causing the stall, given the recent update to OpenClaw and the introduction of new models.

Example

No specific code snippet can be provided without more information on the OpenClaw configuration or the custom services that were disabled.

Notes

The exact cause of the issue is unclear, and more information about the OpenClaw configuration, custom services, and model setup may be necessary to provide a definitive solution.

Recommendation

Apply a workaround by adjusting the scheduling or timing-related configurations in OpenClaw or its dependencies, as upgrading to a fixed version is not clearly implied in the issue.

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…

FAQ

Expected behavior

this happened starting around April 3rd midnight when i was trying to figure out how to get gemma 4 working on my system and i also updated my openclaw same time cause i realized it was on a old version of it.

#api#installation#tensor shape#autograd error#model save/load

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]: [WSL2] Global 30-min gateway stall (:29/:59) affects Telegram + Control UI [1 comments, 1 participants]