Issue Station
Sign In
Tools hereToolbox

openclaw - ✅(Solved) Fix [Bug]: Channels (Telegram/WhatsApp) not loading in v2026.4.2 - empty table in status [1 pull requests, 1 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#60646•Fetched 2026-04-08 02:48:47
View on GitHub
Comments
1
Participants
2
Timeline
4
Reactions
0
Author
ja16779ja16779
Participants
ja16779ja16779yetvalyetval
Timeline (top)
labeled ×2commented ×1cross-referenced ×1

Channels Empty

Root Cause

Channels Empty

Fix Action

Fixed

PR fix notes

PR #60700: channels/telegram: fix hasConfiguredState to detect config-file botToken, tokenFile, and accounts

Description (problem / solution / changelog)

Fixes #60646

Summary

  • hasConfiguredState in extensions/telegram/contract-surfaces.ts only checked the TELEGRAM_BOT_TOKEN env var, ignoring botToken, tokenFile, and accounts set via config file
  • This caused isChannelConfigured() to return false for config-file-only Telegram setups, which made shouldLoadChannelPluginInSetupRuntime() treat the channel as unconfigured — resulting in an empty status table
  • Fix: extend hasConfiguredState to also check cfg.channels.telegram.botToken, tokenFile, and accounts
  • Added three new tests to src/config/channel-configured.test.ts covering each config-file detection path

Test plan

  • pnpm test src/config/channel-configured.test.ts — all new cases pass
  • Manual: set channels.telegram.botToken in config (no env var) → channels table populates correctly in openclaw channels status

Changed files

  • extensions/telegram/contract-surfaces.ts (modified, +25/-3)
  • src/config/channel-configured.test.ts (modified, +26/-0)

Code Example

{                                                                                                                                                             
     "channels": {                                                                                                                                               
       "telegram": {                                                                                                                                             
         "botToken": "8059822025:AAHBLAa5thxa4e2hKxbwcwLfxMu1LUIxwdY",                                                                                           
         "dmPolicy": "pairing",                                                                                                                                  
         "enabled": true                                                                                                                                         
       },                                                                                                                                                        
       "whatsapp": {                                                                                                                                             
         "accounts": { "default": { "enabled": true } },                                                                                                         
         "enabled": true                                                                                                                                         
       }                                                                                                                                                         
     }                                                                                                                                                           
   }                     

### Expected behavior

channels table should show telegram and whatsapp entries with "ready" state.

### Actual behavior

Channels table is completely empty. No initialization logs for Telegram or WhatsApp.

### OpenClaw version

OpenClaw: 2026.4.2

### Operating system

OS: Linux 6.17.0-20-generic (x64)

### Install method

_No response_

### Model

ollama/kimi-k2.5:cloud

### Provider / routing chain

openclaw

### Additional provider/model setup details

_No response_

### Logs, screenshots, and evidence
RAW_BUFFERClick to expand / collapse

Bug type

Regression (worked before, now fails)

Beta release blocker

No

Summary

Channels Empty

Steps to reproduce

Description:
Gateway starts successfully but does not load configured channels even though openclaw config validate confirms configuration is valid.

Environment:

  • OpenClaw version: 2026.4.2
  • OS: Linux 6.17.0-20-generic (x64)
  • Node.js: v22.22.2
  • Gateway mode: local (loopback)

Steps to Reproduce:

  1. Configure channels.telegram with valid botToken
  2. Run openclaw config validate → OK
  3. Run openclaw gateway restart
  4. Run openclaw status → Channels table is empty

Configuration:

{                                                                                                                                                             
  "channels": {                                                                                                                                               
    "telegram": {                                                                                                                                             
      "botToken": "8059822025:AAHBLAa5thxa4e2hKxbwcwLfxMu1LUIxwdY",                                                                                           
      "dmPolicy": "pairing",                                                                                                                                  
      "enabled": true                                                                                                                                         
    },                                                                                                                                                        
    "whatsapp": {                                                                                                                                             
      "accounts": { "default": { "enabled": true } },                                                                                                         
      "enabled": true                                                                                                                                         
    }                                                                                                                                                         
  }                                                                                                                                                           
}                     

### Expected behavior

channels table should show telegram and whatsapp entries with "ready" state.

### Actual behavior

Channels table is completely empty. No initialization logs for Telegram or WhatsApp.

### OpenClaw version

OpenClaw: 2026.4.2

### Operating system

OS: Linux 6.17.0-20-generic (x64)

### Install method

_No response_

### Model

ollama/kimi-k2.5:cloud

### Provider / routing chain

openclaw

### Additional provider/model setup details

_No response_

### Logs, screenshots, and evidence

```shell

Impact and severity

No response

Additional information

No response

extent analysis

TL;DR

  • Verify the configuration file for any syntax errors or missing required fields, and check the gateway logs for any initialization errors.

Guidance

  • Review the openclaw configuration file to ensure that all required fields for channels.telegram and channels.whatsapp are present and correctly formatted.
  • Check the gateway logs for any errors or warnings related to channel initialization, as the absence of initialization logs suggests a potential issue during the startup process.
  • Run openclaw config validate with increased verbosity (if available) to see if it reports any issues that might not be visible in the standard output.
  • Consider comparing the current configuration with a known working version to identify any recent changes that might be causing the issue.

Example

No specific code example is provided due to the lack of direct code references in the issue, but ensuring the configuration JSON is correctly formatted and complete is crucial.

Notes

The issue seems to be related to the configuration or the initialization process of the channels. Without access to the logs or more detailed error messages, it's challenging to provide a precise fix. The steps outlined are aimed at troubleshooting and potentially identifying the root cause.

Recommendation

  • Apply workaround: Carefully review and validate the configuration to ensure all necessary settings are correctly set for both Telegram and WhatsApp channels, as the issue might be related to a misconfiguration or an error in the configuration file that is not caught by the openclaw config validate command.

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

channels table should show telegram and whatsapp entries with "ready" state.

#index setup#retrieval issue#search optimization#API routing#API middleware

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING