# NousResearch/hermes-agent · Telegram start_polling failures during conflict retry and reconnect

## Open now

- Nothing open on GitHub.

These items all concern the Telegram integration's start_polling step failing, including after a conflict retry, which may leave the gateway running without active polling. One member appears to be a pull request proposing to route that failure into a network reconnect process; the other two are bug reports, and their details are not shown here.

## TL;DR

- 3 member(s): 0 open issue(s), 2 closed issue(s), 0 open PR(s), 0 merged PR(s), 1 PR(s) closed without merging.
- No fix has been merged to main; one or more PRs were attempted (see below).
- **Recommended:** review the prior/competing PR(s) below. A fix was attempted but not merged; your case may extend or revive that work.

## Maintainer resolution verdict

- Internal-tracker verdict over this cluster's issue members: `unresolved`. This is distinct from the fix status above. Weigh it yourself.

## How this cluster was grouped

- Link evidence (`STRUCTURAL_PARTIAL`): some members are connected by structural evidence (shared changed files, or a closing/superseded reference); the rest are joined by an automated relevance judgement over their text.
- Members outside that structural core may belong to a different underlying problem.
- Pairwise link density `0.45`: the share of member pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36. `1.00` means every pair is linked.

## Closed / duplicate issues

- #6153: \[Bug\]: Telegram bug start_polling failed
- #25221: Telegram gateway can stay alive with dead polling after conflict retry start_polling failure

## Prior & competing PRs

- **#25285: fix(telegram): route conflict-retry start_polling failure into network reconnect ladder**. closed without merge
  - maintainer direction: category `duplicate_of`; implication `duplicate`; refs `#25232`

## Fix status

- No merged fix on record.
- Subsystem: `gateway`