{"repo":"NousResearch/hermes-agent","public_id":"6153","display_label":"Telegram start_polling failures during conflict retry and reconnect","summary":"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.","subsystem":"gateway","counts":{"members":3,"open_issues":0,"open_issues_distinct":0,"open_prs":0,"closed_issues":2,"merged_prs":0,"attempt_prs":1},"landed_fix":null,"resolution":{"state":"unresolved","by":null},"freshness":{"state":"never_verified","last_verified_at":null,"is_stale":false},"grouping":{"backbone":"STRUCTURAL_PARTIAL","link_density":0.4533333333333333},"fix_edges":[],"members":[{"kind":"issue","number":6153,"title":"[Bug]: Telegram bug start_polling failed","url":null,"state":"closed"},{"kind":"issue","number":25221,"title":"Telegram gateway can stay alive with dead polling after conflict retry start_polling failure","url":null,"state":"closed"},{"kind":"pr","number":25285,"title":"fix(telegram): route conflict-retry start_polling failure into network reconnect ladder","url":null,"state":"closed","close_reason":{"refs":[{"kind":"pr","value":"#25232","number":25232}],"category":"duplicate_of","implication":"duplicate"},"merged":false}],"trust":{"default_tier":"verified","includes_suggested":false}}