Issue Station
Sign In
Tools hereToolbox

openclaw - ✅(Solved) Fix [Bug]: [telegram] polling runner stopped (polling stall detected) [1 pull requests, 3 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#64288•Fetched 2026-04-11 06:15:32
View on GitHub
Comments
3
Participants
3
Timeline
10
Reactions
0
Author
athuljayaramathuljayaram
Participants
athuljayaramathuljayaramEronFanEronFanmjamivmjamiv
Timeline (top)
commented ×3labeled ×2renamed ×2cross-referenced ×1

telegram is having frequent issue

Error Message

12:53:14+01:00 [telegram] Polling stall detected (no completed getUpdates for 105.92s); forcing restart. [diag inFlight=0 outcome=error startedAt=1775821858079 finishedAt=1775821888092 durationMs=30013 offset=61638802 error=Network request for 'getUpdates' failed!] 12:53:29+01:00 [telegram] [diag] polling cycle finished reason=polling stall detected inFlight=0 outcome=error startedAt=1775821858079 finishedAt=1775821888092 durationMs=30013 offset=61638802 error=Network request for 'getUpdates' failed!

Root Cause

telegram is having frequent issue

Fix Action

Fixed

PR fix notes

PR #64333: fix: avoid false telegram polling stall restarts

Description (problem / solution / changelog)

Summary

  • count completed getUpdates calls, including recoverable errors, as API liveness for the polling stall watchdog
  • avoid forcing a polling restart while Telegram is still actively retrying after a recent getUpdates failure
  • add regression coverage for the post-error watchdog window

Testing

  • pnpm test -- extensions/telegram/src/polling-session.test.ts

Fixes #64288

Changed files

  • extensions/telegram/src/polling-session.test.ts (modified, +43/-0)
  • extensions/telegram/src/polling-session.ts (modified, +2/-0)
RAW_BUFFERClick to expand / collapse

Bug type

Regression (worked before, now fails)

Beta release blocker

No

Summary

telegram is having frequent issue

Steps to reproduce

just restart gateway and wait

Expected behavior

no issues

Actual behavior

12:53:14+01:00 [telegram] Polling stall detected (no completed getUpdates for 105.92s); forcing restart. [diag inFlight=0 outcome=error startedAt=1775821858079 finishedAt=1775821888092 durationMs=30013 offset=61638802 error=Network request for 'getUpdates' failed!] 12:53:29+01:00 [telegram] Polling runner stop timed out after 15s; forcing restart cycle. 12:53:29+01:00 [telegram] [diag] polling cycle finished reason=polling stall detected inFlight=0 outcome=error startedAt=1775821858079 finishedAt=1775821888092 durationMs=30013 offset=61638802 error=Network request for 'getUpdates' failed! 12:53:29+01:00 [telegram] polling runner stopped (polling stall detected); restarting in 30s. 12:54:14+01:00 [telegram] [diag] rebuilding transport for next polling cycle 12:54:15+01:00 [skills] Skipping skill path that resolves outside its configured root. 12:54:15+01:00 [telegram] menu text exceeded the conservative 5700-character payload budget; shortening descriptions to keep 73 commands visible.

OpenClaw version

2026.4.9

Operating system

Windows 11

Install method

powershell

Model

minimax

Provider / routing chain

local

Additional provider/model setup details

No response

Logs, screenshots, and evidence

Impact and severity

No response

Additional information

No response

extent analysis

TL;DR

The issue with frequent Telegram problems may be related to network request failures, and a potential fix could involve adjusting the polling settings or handling network errors.

Guidance

  • Investigate the network connectivity and stability to ensure it's not causing the "Network request for 'getUpdates' failed!" error.
  • Check the Telegram API documentation for any known issues or limitations related to polling and getUpdates requests.
  • Consider implementing retry mechanisms or exponential backoff for handling network request failures.
  • Review the polling settings and adjust the timeout values if necessary to prevent polling stall detections.

Example

No specific code snippet can be provided without more context, but an example of a retry mechanism in a hypothetical polling function could be:

import time

def poll_telegram():
    max_retries = 3
    retry_delay = 5  # seconds
    for attempt in range(max_retries):
        try:
            # Make the getUpdates request
            response = make_request()
            if response.success:
                break
        except NetworkError:
            if attempt < max_retries - 1:
                time.sleep(retry_delay)
                retry_delay *= 2  # exponential backoff
            else:
                raise

## Notes
The provided logs suggest a potential issue with network requests, but without more information about the environment and setup, it's difficult to provide a more specific solution.

## Recommendation
Apply a workaround by implementing a retry mechanism or adjusting the polling settings to handle network request failures, as the root cause of the issue is likely related to network stability or API limitations.

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

no issues

#retriever error#indexing error#inference speed#output truncation#response parsing

Still need to ship something?

×6

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

Back to top recommendations

TRENDING