openclaw - 💡(How to fix) Fix [Bug]: Telegram stop messages after upgrade to openclaw upgrade (2026.04.29) [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#76133Fetched 2026-05-03 04:41:57
View on GitHub
Comments
2
Participants
2
Timeline
6
Reactions
2
Author
Timeline (top)
commented ×2labeled ×2closed ×1unsubscribed ×1

After upgrading from 2026.04.26 to 2026.04.29, telegram integration stopped. The messa is not shown anymore: 15:05:37 [heartbeat] started 15:05:38 [telegram] [default] starting provider (@openclaw_ai_nia_bot)

After downgrade: 2026.04.29 to 2026.04.26

Root Cause

After upgrading from 2026.04.26 to 2026.04.29, telegram integration stopped. The messa is not shown anymore: 15:05:37 [heartbeat] started 15:05:38 [telegram] [default] starting provider (@openclaw_ai_nia_bot)

After downgrade: 2026.04.29 to 2026.04.26

RAW_BUFFERClick to expand / collapse

Bug type

Regression (worked before, now fails)

Beta release blocker

No

Summary

After upgrading from 2026.04.26 to 2026.04.29, telegram integration stopped. The messa is not shown anymore: 15:05:37 [heartbeat] started 15:05:38 [telegram] [default] starting provider (@openclaw_ai_nia_bot)

After downgrade: 2026.04.29 to 2026.04.26

Steps to reproduce

In powershell 1 - openclaw gateway stop 2 - openclaw update

Expected behavior

After upgrading the integration telegram, it should run normally

Actual behavior

The telegram did not respond, and the message is not shown: 15:05:38 [telegram] [default] starting provider (@openclaw_ai_nia_bot)

OpenClaw version

2026.04.29

Operating system

Windws Server build 26100 = 24H2 (32 GB de RAM, 8 Cores)

Install method

npm

Model

ollama/Kimi 2.6

Provider / routing chain

openclaw -> ollama cloud -> kimi

Additional provider/model setup details

No response

Logs, screenshots, and evidence

Impact and severity

Affected: Telegram bot Severity: High (no replies) Frequency: 10/10 (many gateway restart) Consequence: Agents

openclaw-2026-05-02 - Copy.log

do not respond

Additional information

No response

extent analysis

TL;DR

Downgrade to version 2026.04.26 to restore Telegram integration functionality.

Guidance

  • The issue is likely caused by a regression introduced in version 2026.04.29, as the integration works correctly in version 2026.04.26.
  • To verify the issue, try downgrading to version 2026.04.26 and check if the Telegram integration starts working again.
  • Review the logs from the affected version (2026.04.29) to see if there are any error messages related to the Telegram integration.
  • If downgrading is not a viable long-term solution, consider reporting the issue to the OpenClaw developers to get a fix for the regression in a future version.

Notes

The provided information does not include specific error messages or detailed logs, which could help identify the root cause of the issue. The suggested downgrade is based on the fact that the integration worked in version 2026.04.26 and stopped working after upgrading to 2026.04.29.

Recommendation

Apply workaround: Downgrade to version 2026.04.26, as it is the only known version that works correctly with the Telegram integration. This will allow the integration to function until a fix is available for the regression in version 2026.04.29.

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

After upgrading the integration telegram, it should run normally

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]: Telegram stop messages after upgrade to openclaw upgrade (2026.04.29) [2 comments, 2 participants]