openclaw - 💡(How to fix) Fix [Bug]: status channel summary is empty while Telegram health probe is OK on v2026.4.25 [1 comments, 1 participants]

Official PRs (…)
ON THIS PAGE

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#72906Fetched 2026-04-28 06:30:29
View on GitHub
Comments
1
Participants
1
Timeline
2
Reactions
0
Participants
Timeline (top)
commented ×1cross-referenced ×1

After upgrading a Linux VPS from OpenClaw 2026.4.24 to 2026.4.25, openclaw status --deep shows Telegram as healthy in the Health section, but the Channels table is empty.

This makes the status output look like no channels are enabled/running, even though Telegram is configured and the health probe succeeds.

Root Cause

After upgrading a Linux VPS from OpenClaw 2026.4.24 to 2026.4.25, openclaw status --deep shows Telegram as healthy in the Health section, but the Channels table is empty.

This makes the status output look like no channels are enabled/running, even though Telegram is configured and the health probe succeeds.

Code Example

Gateway ... app 2026.4.25 ... reachable
Gateway service systemd installed · enabled · running
Memory enabled (plugin memory-core) · unavailable

Channels
┌──────────┬─────────┬────────┬────────────────────────────────────────────────────────────────────────────────────────┐
ChannelEnabledStateDetail├──────────┼─────────┼────────┼────────────────────────────────────────────────────────────────────────────────────────┤
└──────────┴─────────┴────────┴────────────────────────────────────────────────────────────────────────────────────────┘

Health
┌──────────┬───────────┬───────────────────────────────────────────────────────────────────────────────────────────────┐
ItemStatusDetail├──────────┼───────────┼───────────────────────────────────────────────────────────────────────────────────────────────┤
Gateway  │ reachable │ ...TelegramOKok (@...:default:...)└──────────┴───────────┴───────────────────────────────────────────────────────────────────────────────────────────────┘
RAW_BUFFERClick to expand / collapse

Summary

After upgrading a Linux VPS from OpenClaw 2026.4.24 to 2026.4.25, openclaw status --deep shows Telegram as healthy in the Health section, but the Channels table is empty.

This makes the status output look like no channels are enabled/running, even though Telegram is configured and the health probe succeeds.

Environment

  • OpenClaw: 2026.4.25 (aa36ee6)
  • OS: Linux 6.6.117-45.2.oc9.x86_64 x64
  • Node: 24.14.0
  • Gateway: systemd, loopback bind 127.0.0.1:18789
  • Channel: Telegram

Evidence

openclaw status --deep --timeout 10000 reports:

Gateway ... app 2026.4.25 ... reachable
Gateway service systemd installed · enabled · running
Memory enabled (plugin memory-core) · unavailable

Channels
┌──────────┬─────────┬────────┬────────────────────────────────────────────────────────────────────────────────────────┐
│ Channel  │ Enabled │ State  │ Detail                                                                                 │
├──────────┼─────────┼────────┼────────────────────────────────────────────────────────────────────────────────────────┤
└──────────┴─────────┴────────┴────────────────────────────────────────────────────────────────────────────────────────┘

Health
┌──────────┬───────────┬───────────────────────────────────────────────────────────────────────────────────────────────┐
│ Item     │ Status    │ Detail                                                                                        │
├──────────┼───────────┼───────────────────────────────────────────────────────────────────────────────────────────────┤
│ Gateway  │ reachable │ ...                                                                                           │
│ Telegram │ OK        │ ok (@...:default:...)                                                                          │
└──────────┴───────────┴───────────────────────────────────────────────────────────────────────────────────────────────┘

openclaw status --json --deep also contains channelSummary: [] while health.channels.telegram.probe.ok is true.

Expected behavior

If Telegram is configured and the probe succeeds, the Channels table / channelSummary should include Telegram with an OK/probed state, or the output should clearly distinguish “configured channel summary unavailable” from “no enabled channels”.

Actual behavior

The human-readable Channels table is empty, while the Health table shows Telegram OK.

Impact

This can confuse upgrade verification, especially after a production upgrade where operators rely on openclaw status --deep to decide whether channels survived the restart.

extent analysis

TL;DR

The issue might be resolved by checking the configuration and plugin settings for Telegram in OpenClaw version 2026.4.25.

Guidance

  • Verify that the Telegram plugin is correctly configured and enabled in the OpenClaw settings.
  • Check the openclaw logs for any errors or warnings related to the Telegram plugin or channel initialization.
  • Compare the configuration files between OpenClaw versions 2026.4.24 and 2026.4.25 to identify any changes that might affect the Telegram channel.
  • Run openclaw status --json --deep and check the channelSummary field to see if it contains any information about the Telegram channel.

Example

No code snippet is provided as the issue seems to be related to configuration or plugin settings.

Notes

The issue might be specific to the OpenClaw version 2026.4.25 or the Linux environment. Further investigation is needed to determine the root cause.

Recommendation

Apply workaround: Check and adjust the Telegram plugin configuration and settings to ensure it is correctly enabled and initialized in OpenClaw version 2026.4.25. This is recommended because the issue seems to be related to the plugin or configuration rather than a version-specific bug.

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

If Telegram is configured and the probe succeeds, the Channels table / channelSummary should include Telegram with an OK/probed state, or the output should clearly distinguish “configured channel summary unavailable” from “no enabled channels”.

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]: status channel summary is empty while Telegram health probe is OK on v2026.4.25 [1 comments, 1 participants]