Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix [Bug]: Regression (worked in v4.1, broken in v4.2) [2 comments, 2 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#60185•Fetched 2026-04-08 02:35:19
View on GitHub
Comments
2
Participants
2
Timeline
6
Reactions
2
Author
sieuthisanphamsieuthisanpham
Participants
BruceMacDBruceMacDsieuthisanphamsieuthisanpham
Assignees
BruceMacDBruceMacD
Timeline (top)
commented ×2labeled ×2assigned ×1closed ×1

Telegram channel stops receiving messages silently after upgrading from OpenClaw 2026.4.1 to 2026.4.2. No error is shown in logs or on Telegram. Downgrading back to 2026.4.1 immediately restores Telegram functionality.

Error Message

Telegram channel stops receiving messages silently after upgrading from OpenClaw 2026.4.1 to 2026.4.2. No error is shown in logs or on Telegram. Downgrading back to 2026.4.1 immediately restores Telegram functionality. 5. Bot does not reply. No error appears in Telegram or in openclaw logs --follow.

  • Bot is completely silent — no reply, no error message.

Root Cause

Telegram channel stops receiving messages silently after upgrading from OpenClaw 2026.4.1 to 2026.4.2. No error is shown in logs or on Telegram. Downgrading back to 2026.4.1 immediately restores Telegram functionality.

Fix Action

Fix / Workaround

  1. Run OpenClaw 2026.4.1 with ollama/kimi-k2.5:cloud — Telegram works normally.
  2. Upgrade to OpenClaw 2026.4.2 via npm install -g openclaw@latest.
  3. Restart gateway: openclaw gateway restart.
  4. Send any message to the Telegram bot.
  5. Bot does not reply. No error appears in Telegram or in openclaw logs --follow.
**Workaround**
Downgrade to 2026.4.1:

Code Example

**Workaround**
Downgrade to 2026.4.1:

npm install -g openclaw@2026.4.1
openclaw gateway restart

Telegram works immediately after downgrade.

**Additional notes**
- Telegram config in `openclaw.json` is intact and correct (botToken, allowFrom, dmPolicy, enabled: true).
- Issue is 100% reproducible by upgrading/downgrading between the two versions.
- Switching models does not fix the issue — tested with multiple models.
RAW_BUFFERClick to expand / collapse

Bug type

Regression (worked before, now fails)

Beta release blocker

No

Summary

Telegram channel stops receiving messages silently after upgrading from OpenClaw 2026.4.1 to 2026.4.2. No error is shown in logs or on Telegram. Downgrading back to 2026.4.1 immediately restores Telegram functionality.

Steps to reproduce

  1. Run OpenClaw 2026.4.1 with ollama/kimi-k2.5:cloud — Telegram works normally.
  2. Upgrade to OpenClaw 2026.4.2 via npm install -g openclaw@latest.
  3. Restart gateway: openclaw gateway restart.
  4. Send any message to the Telegram bot.
  5. Bot does not reply. No error appears in Telegram or in openclaw logs --follow.

Expected behavior

Telegram bot should receive and reply to messages, same as in v4.1.

Actual behavior

  • Bot is completely silent — no reply, no error message.
  • openclaw channels status shows no Telegram channel info.
  • openclaw logs --follow shows no activity when a message is sent via Telegram.
  • Web UI (http://127.0.0.1:18789) continues to work normally.
  • Gateway status shows correct bind: openclaw-gateway (*:18789).

OpenClaw version

OpenClaw version: 2026.4.2 (d74a122)

Operating system

Linux (Ubuntu)

Install method

npm global

Model

ollama/kimi-k2.5:cloud

Provider / routing chain

ollama → kimi-k2.5:cloud → Telegram (polling)

Additional provider/model setup details

  • Provider: Ollama (installed via ollama launch openclaw --model kimi-k2.5:cloud)
  • Model: kimi-k2.5:cloud (cloud model, no local GPU required)
  • Ollama base URL: http://localhost:11434
  • OpenClaw launched via: ollama launch openclaw
  • No custom provider config in openclaw.json — Ollama auto-configured during onboarding

Logs, screenshots, and evidence

**Workaround**
Downgrade to 2026.4.1:

npm install -g [email protected]
openclaw gateway restart

Telegram works immediately after downgrade.

**Additional notes**
- Telegram config in `openclaw.json` is intact and correct (botToken, allowFrom, dmPolicy, enabled: true).
- Issue is 100% reproducible by upgrading/downgrading between the two versions.
- Switching models does not fix the issue — tested with multiple models.

Impact and severity

No response

Additional information

No response

extent analysis

TL;DR

Downgrade to OpenClaw version 2026.4.1 to restore Telegram functionality.

Guidance

  • Verify that the openclaw.json configuration file remains unchanged and correct after the upgrade, especially the Telegram config section.
  • Check for any differences in the ollama and kimi-k2.5:cloud model configurations between OpenClaw versions 2026.4.1 and 2026.4.2.
  • Test the Telegram functionality with a different model to confirm if the issue is model-specific or not.
  • Review the OpenClaw changelog for version 2026.4.2 to identify any changes that might be causing the issue.

Example

No code snippet is provided as the issue seems to be related to a version-specific bug rather than a code error.

Notes

The issue appears to be a regression introduced in OpenClaw version 2026.4.2, and downgrading to version 2026.4.1 resolves the issue. It is recommended to wait for a patch or a new version that addresses this regression.

Recommendation

Apply the workaround by downgrading to OpenClaw version 2026.4.1, as it immediately restores Telegram functionality.

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

Telegram bot should receive and reply to messages, same as in v4.1.

#latency issue#model loading#dependency error#configuration error#environment variable

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]: Regression (worked in v4.1, broken in v4.2) [2 comments, 2 participants]