openclaw - ✅(Solved) Fix Telegram health endpoint shows running:false while bot is functional [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#55482Fetched 2026-04-08 01:39:03
View on GitHub
Comments
0
Participants
1
Timeline
2
Reactions
0
Participants
Timeline (top)
cross-referenced ×1referenced ×1

The health status endpoint reports running: false and tokenSource: none for the Telegram integration, even though the bot is fully operational and responding to messages.

Root Cause

The health status endpoint reports running: false and tokenSource: none for the Telegram integration, even though the bot is fully operational and responding to messages.

Fix Action

Fixed

PR fix notes

PR #55550: fix: report correct Telegram bot health status (#55482)

Description (problem / solution / changelog)

Summary

  • Fixes #55482
  • Telegram health endpoint incorrectly reported running: false and tokenSource: none
  • Fixed health check to accurately reflect the bot's operational state

Test plan

  • Start Telegram bot integration
  • Check health endpoint and verify it shows running: true when bot is active

Changed files

  • extensions/telegram/src/channel.test.ts (modified, +64/-0)
  • extensions/telegram/src/channel.ts (modified, +11/-1)
RAW_BUFFERClick to expand / collapse

Description

The health status endpoint reports running: false and tokenSource: none for the Telegram integration, even though the bot is fully operational and responding to messages.

Steps to Reproduce

  1. Configure Telegram bot integration (working, sending/receiving messages)
  2. Check health endpoint
  3. Observe running: false / tokenSource: none

Expected Behavior

Health endpoint should reflect actual operational state — running: true when the bot is actively processing messages.

Actual Behavior

Shows running: false / tokenSource: none despite the bot working correctly. Cosmetic but misleading for monitoring and dashboards.

Environment

  • OpenClaw (latest)
  • macOS (Mac mini, always-on)
  • Telegram bot integration

extent analysis

Fix Plan

The fix involves updating the health status endpoint to correctly reflect the operational state of the Telegram bot integration.

Steps to Fix

  • Update the TelegramIntegration class to include a isRunning method that checks the bot's actual operational state.
  • Modify the health status endpoint to call the isRunning method and update the running field accordingly.
  • Ensure the tokenSource field is correctly populated when the bot is operational.

Example Code

class TelegramIntegration:
    # ...

    def is_running(self):
        # Check if the bot is actively processing messages
        return self.bot.get_updates() is not None

# In the health status endpoint
def get_health_status():
    telegram_integration = TelegramIntegration()
    health_status = {
        'running': telegram_integration.is_running(),
        'tokenSource': 'telegram' if telegram_integration.is_running() else 'none'
    }
    return health_status

Verification

  • Restart the application and verify that the health status endpoint reports running: true when the bot is operational.
  • Check that the tokenSource field is correctly populated as telegram when the bot is running.

Extra Tips

  • Consider adding logging to track changes to the bot's operational state and health status endpoint updates.
  • Review the TelegramIntegration class to ensure it correctly handles edge cases, such as network errors or bot downtime.

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…

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 Telegram health endpoint shows running:false while bot is functional [1 pull requests, 1 participants]