Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix Telegram polling fails to start after gateway restart (LaunchAgent) [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#61712•Fetched 2026-04-08 02:55:31
View on GitHub
Comments
0
Participants
1
Timeline
0
Reactions
0
Author
longxiahsiao-sketchlongxiahsiao-sketch
Participants
longxiahsiao-sketchlongxiahsiao-sketch

Error Message

  • No error messages in gateway log

Code Example

"channels": {
  "telegram": {
    "enabled": true,
    "botToken": "YOUR_TOKEN"
  }
}
RAW_BUFFERClick to expand / collapse

Bug Description

Telegram polling fails to start after gateway restart on macOS with LaunchAgent.

Environment

  • OpenClaw: 2026.4.2
  • OS: macOS
  • Service: LaunchAgent (launchd)

Steps to Reproduce

  1. Configure channels.telegram with botToken in openclaw.json
  2. Run launchctl stop ai.openclaw.gateway && sleep 3 && launchctl start ai.openclaw.gateway
  3. Gateway starts successfully (PID visible)
  4. Telegram channel does not initialize - no entries in log file

Expected Behavior

Telegram polling should start and connect to the bot.

Actual Behavior

  • Gateway starts normally
  • No Telegram initialization in logs
  • openclaw status shows Channels table empty
  • Bot token verified valid via direct API call

Configuration

"channels": {
  "telegram": {
    "enabled": true,
    "botToken": "YOUR_TOKEN"
  }
}

Additional Context

  • This happens consistently on every restart
  • The bot token is valid (verified via getUpdates API)
  • No error messages in gateway log
  • Memory plugin (memory-lancedb-pro) initializes fine
  • Gateway restart is being deferred when active webchat connections exist

extent analysis

TL;DR

The Telegram polling issue after gateway restart on macOS with LaunchAgent may be resolved by verifying the configuration and environment variables.

Guidance

  • Check the openclaw.json configuration file for any typos or incorrect settings, especially the botToken value.
  • Verify that the launchctl commands are correctly stopping and starting the ai.openclaw.gateway service, and that the service is properly configured to run with the correct environment variables.
  • Investigate if the sleep 3 delay between stopping and starting the service is sufficient, and consider increasing the delay if necessary.
  • Review the gateway log files for any subtle error messages or warnings that may indicate the cause of the issue.

Example

No code snippet is provided as it is not clearly supported by the issue.

Notes

The issue may be related to the specific environment or configuration, and further investigation is needed to determine the root cause. The fact that the bot token is valid and the memory plugin initializes fine suggests that the issue may be related to the Telegram channel configuration or the LaunchAgent service.

Recommendation

Apply workaround: Verify the configuration and environment variables, and consider increasing the delay between stopping and starting the service. This is because the issue is likely related to the specific environment or configuration, and a workaround may be necessary to resolve the issue until a permanent fix is found.

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#inference speed#output truncation#response parsing#generation 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