# NousResearch/hermes-agent · Telegram polling recovery confirmation logging gap

## Open now

- Nothing open on GitHub.

A bug was identified where the log line 'health pending getUpdates progress' appears as the final message in both healthy and hung Telegram polling states, making recovery indistinguishable from failure. Related fixes address logging the first confirmed getUpdates progress per generation.

## TL;DR

- 3 member(s): 0 open issue(s), 1 closed issue(s), 0 open PR(s), 1 merged PR(s), 1 PR(s) closed without merging.
- A fix was merged to main in PR #90560. Verify it addresses your case.
- **Recommended:** read PR #90560 (and any competing PRs below) before filing. Confirm the merged change covers your symptom.

## Maintainer resolution verdict

- Internal-tracker verdict over this cluster's issue members: `resolved` · deciding PR(s): `pr-90560`. This is distinct from the fix status above. Weigh it yourself.

## How this cluster was grouped

- Link evidence (`STRUCTURAL_SPANNING`): every member is connected by structural evidence: shared changed files, or a closing/superseded reference.
- Pairwise link density `0.67`: 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

- #90504: \[Bug\]: Telegram polling recovery is never positively confirmed — "health pending getUpdates progress" is the terminal log line in both the healthy and the hung case

## Prior & competing PRs

- **#90560: fix(telegram): log the first confirmed getUpdates progress per generation**. merged to main · fix tier `verified`
  - maintainer direction: category `merged`
  - files: `plugins/platforms/telegram/adapter.py`, `tests/gateway/test_telegram_polling_health_confirmation.py`
- **#90521: fix(telegram): log the first confirmed getUpdates progress per generation**. closed without merge
  - maintainer direction: category `merged_via`; implication `superseded`; refs `#90560`

## Fix status

- Merged to main in PR #90560 (cited above). No release data is tracked. Verify downstream.
- Fix last verified (merged) `2026-08-20`.