Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix openclaw doctor reports 'Telegram: not configured' despite Telegram channel working correctly [4 comments, 3 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#44539•Fetched 2026-04-08 00:45:31
View on GitHub
Comments
4
Participants
3
Timeline
5
Reactions
0
Author
tamaosamutamaosamu
Participants
clawjasper56clawjasper56lunaviva211-sketchlunaviva211-sketchtamaosamutamaosamu
Timeline (top)
commented ×4cross-referenced ×1

openclaw doctor reports Telegram: not configured in the channel probe section, even though the Telegram channel is fully operational.

Root Cause

openclaw doctor reports Telegram: not configured in the channel probe section, even though the Telegram channel is fully operational.

Code Example

{
  "channels": {
    "telegram": {
      "enabled": true,
      "botToken": "<redacted>",
      "accounts": {
        "<chatId>": {
          "name": "...",
          "enabled": true,
          "botToken": "<redacted>"
        },
        "default": {
          "botToken": "<redacted>"
        }
      }
    }
  },
  "plugins": {
    "entries": {
      "telegram": { "enabled": true }
    }
  }
}
RAW_BUFFERClick to expand / collapse

Description

openclaw doctor reports Telegram: not configured in the channel probe section, even though the Telegram channel is fully operational.

Current Behavior

  • openclaw doctor → Telegram: not configured
  • openclaw status → Telegram │ ON │ OK │ token config×2 (8450…_SqQ · len 46) · accounts 2/2
  • Bot is actively receiving and sending Telegram messages

Configuration

{
  "channels": {
    "telegram": {
      "enabled": true,
      "botToken": "<redacted>",
      "accounts": {
        "<chatId>": {
          "name": "...",
          "enabled": true,
          "botToken": "<redacted>"
        },
        "default": {
          "botToken": "<redacted>"
        }
      }
    }
  },
  "plugins": {
    "entries": {
      "telegram": { "enabled": true }
    }
  }
}

Expected Behavior

openclaw doctor should report Telegram as configured/OK when openclaw status shows it as ON/OK.

Steps to Reproduce

  1. Configure Telegram channel with botToken at both top-level and account level
  2. Verify Telegram is working (send/receive messages)
  3. Run openclaw doctor
  4. Observe "Telegram: not configured" in channel probe section
  5. Run openclaw status and see Telegram is ON/OK

Environment

  • OpenClaw version: 2026.3.11
  • OS: macOS 26.2 (arm64)
  • Node: v24.12.0

extent analysis

Fix Plan

The issue seems to be related to the configuration validation in openclaw doctor. To fix this, we need to ensure that the Telegram configuration is correctly validated.

Step-by-Step Solution

  1. Update the configuration: Ensure that the botToken is consistently configured at the top-level or account level, but not both.
  2. Validate the configuration: Run openclaw doctor with the --verbose flag to get more detailed output about the configuration validation.
  3. Code changes: If the issue persists, update the openclaw code to correctly handle the configuration validation. For example:
// In the openclaw doctor code
if (config.channels.telegram.enabled && config.channels.telegram.botToken) {
  // Telegram is configured
} else if (config.channels.telegram.accounts && Object.keys(config.channels.telegram.accounts).length > 0) {
  // Telegram accounts are configured
} else {
  // Telegram is not configured
}

Verification

Run openclaw doctor again to verify that the issue is fixed. The output should show Telegram: OK in the channel probe section.

Extra Tips

  • Ensure that the botToken is correctly configured and not expired.
  • Check the openclaw documentation for any specific configuration requirements.
  • If the issue persists, try resetting the openclaw configuration to its default state.

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…
#api#ssr#installation#tensor shape#autograd error#model compatibility#GPU setup#container setup#orchestration issue#cache issue

Still need to ship something?

×6

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

Back to top recommendations

TRENDING