Issue Station
Sign In
Tools hereToolbox

openclaw - ✅(Solved) Fix [Bug]: Slack and Telegram show as configured, but no channel accounts are loaded and `status --deep` shows an empty Channels table [1 pull requests, 1 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#55032•Fetched 2026-04-08 01:33:27
View on GitHub
Comments
0
Participants
1
Timeline
5
Reactions
0
Author
thejackluothejackluo
Participants
thejackluothejackluo
Timeline (top)
cross-referenced ×2labeled ×2subscribed ×1

On OpenClaw 2026.3.24, Slack and Telegram appear configured in the channel setup flow, but no channel accounts are loaded at runtime and openclaw status --deep shows an empty Channels table.

Root Cause

Observed after local config was cleared and re-entered. Multiple repair/reconfigure attempts did not repopulate channel accounts. I am intentionally avoiding a root-cause claim here because I do not have direct evidence for the exact failure mechanism.

PR fix notes

PR #55014: telegram: rebuild transport after stalled polling cycles

Description (problem / solution / changelog)

Summary

This draft PR builds on the Telegram polling investigation and takes the next recovery step: once a polling cycle is identified as stalled or fails through a polling-network recovery path, the next polling cycle rebuilds the Telegram transport instead of reusing the previous one.

Why draft

This change affects recovery behavior, not just diagnostics. I want to keep the branch and PR ready for review, but test it locally in a real deployment for a few days before marking it ready.

What this changes

  • marks the current transport as dirty after:
    • watchdog-detected polling stalls
    • recoverable polling network errors
    • unhandled polling network failures that trigger forced restart handling
  • rebuilds the Telegram transport on the next polling cycle when marked dirty
  • keeps the richer polling diagnostics and state-aware stall detection needed to verify behavior in production

Intended effect

If a request wedges in a way that survives normal abort/stop handling, the next cycle should no longer inherit the possibly-bad dispatcher/socket/transport state from the previous cycle.

Local test plan before ready-for-review

  • run in a real Telegram deployment for several days
  • compare stall frequency before/after
  • watch for reduced repeated polling stalls
  • confirm no new or recovery regressions
  • confirm transport rebuild logs correlate with successful recovery

Notes

This is intentionally opened as a draft first. I plan to validate it locally before requesting full upstream review.

Changed files

  • extensions/telegram/src/monitor.ts (modified, +8/-3)
  • extensions/telegram/src/polling-session.ts (modified, +89/-8)

Code Example

- `openclaw status --deep` shows:
  - OpenClaw 2026.3.24 (cff6dc9)
  - Linux 6.17.0-1007-aws (x64) · node 22.22.1
  - Gateway reachable
  - Empty Channels table
- `openclaw configure --section channels` shows:
  - Telegram: configured
  - Slack: configured
  - Accounts: 0
- `openclaw channels list` shows no chat channels.
RAW_BUFFERClick to expand / collapse

Bug type

Regression (worked before, now fails)

Summary

On OpenClaw 2026.3.24, Slack and Telegram appear configured in the channel setup flow, but no channel accounts are loaded at runtime and openclaw status --deep shows an empty Channels table.

Steps to reproduce

  1. Start OpenClaw 2026.3.24 on the affected host.
  2. Run openclaw configure --section channels and observe that Slack and Telegram are shown as configured.
  3. Run openclaw status --deep.
  4. Observe that the Channels table is empty.
  5. Run openclaw channels list.
  6. Observe that no chat channels are listed.

Expected behavior

Configured Slack and Telegram channel accounts should appear in runtime channel status and in the Channels table.

Actual behavior

openclaw status --deep shows Gateway reachable, but the Channels table is empty. openclaw channels list shows no chat channels. In the same environment, the setup flow reports Slack and Telegram as configured.

OpenClaw version

2026.3.24

Operating system

Ubuntu 24.04

Install method

NOT_ENOUGH_INFO

Model

global.anthropic.claude-sonnet-4-6

Provider / routing chain

NOT_ENOUGH_INFO

Additional provider/model setup details

Gateway mode is local and reachable at ws://127.0.0.1:18789. Observed session model is global.anthropic.claude-sonnet-4-6. The affected host reports systemd gateway service running.

Logs, screenshots, and evidence

- `openclaw status --deep` shows:
  - OpenClaw 2026.3.24 (cff6dc9)
  - Linux 6.17.0-1007-aws (x64) · node 22.22.1
  - Gateway reachable
  - Empty Channels table
- `openclaw configure --section channels` shows:
  - Telegram: configured
  - Slack: configured
  - Accounts: 0
- `openclaw channels list` shows no chat channels.

Impact and severity

Affected users/systems/channels: Slack and Telegram on the affected gateway Severity: High Frequency: Observed consistently in the reported environment Consequence: Chat channels do not load at runtime, so Slack and Telegram cannot be used from this gateway

Additional information

Observed after local config was cleared and re-entered. Multiple repair/reconfigure attempts did not repopulate channel accounts. I am intentionally avoiding a root-cause claim here because I do not have direct evidence for the exact failure mechanism.

extent analysis

Fix Plan

To resolve the issue of empty Channels table and missing chat channels, we need to reconfigure the channel accounts and ensure they are properly loaded at runtime. Here are the steps:

  • Re-run the configuration command with the --force flag to reinitialize the channel setup:

openclaw configure --section channels --force

* Verify that the channel accounts are reconfigured correctly by checking the output of:
  ```bash
openclaw configure --section channels
  • Update the channel loader script to ensure it is properly loading the configured channels:

File: openclaw/channels/loader.py

import os

def load_channels(): # Load configured channels from environment variables channels = os.environ.get('OPENCLAW_CHANNELS', '').split(',') # Initialize channel accounts accounts = [] for channel in channels: if channel == 'slack': # Initialize Slack channel account accounts.append({'name': 'Slack', 'type': 'slack'}) elif channel == 'telegram': # Initialize Telegram channel account accounts.append({'name': 'Telegram', 'type': 'telegram'}) return accounts

* Restart the OpenClaw service to apply the changes:
  ```bash
sudo systemctl restart openclaw
  • Verify that the Channels table is populated and chat channels are listed by running:

openclaw status --deep openclaw channels list


### Verification
To verify that the fix worked, check the output of `openclaw status --deep` and `openclaw channels list` to ensure that the Channels table is populated and chat channels are listed.

### Extra Tips
* Ensure that the `OPENCLAW_CHANNELS` environment variable is set correctly to include the configured channels (e.g., `slack,telegram`).
* If issues persist, try clearing the local configuration and re-running the setup flow.
* Refer to the OpenClaw documentation for more information on configuring and troubleshooting channel accounts.

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

Configured Slack and Telegram channel accounts should appear in runtime channel status and in the Channels table.

#device allocation#model download#tokenizer error#prompt formatting#chain error

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 - ✅(Solved) Fix [Bug]: Slack and Telegram show as configured, but no channel accounts are loaded and `status --deep` shows an empty Channels table [1 pull requests, 1 participants]