Spam ERROR Log from timeout request update to telegram

[nvt-ak]

BOT is still working. BOT token was not expired and I don't know this error from what?

[kaitranntt]

Tracking note: the broader fix for this setup/runtime failure is being implemented in #633 so channel instances can surface explicit health and failure attribution instead of only running/stopped. The PR for that work will reference both #628 and #633, since #628 is the original user-facing report.

[kaitranntt]

Opened PR #634 to implement the shared channel-health diagnostics follow-up for this report. The PR references both #628 and #633 and includes the design directions considered.

[nvt-ak]

@kaitranntt Here is my current dashboard and channel views

[kaitranntt]

Thanks for the follow-up screenshots — we’ve read them.

This updates our framing a bit: based on what you’ve shown here, this no longer looks primarily like a bad token or missing channel setup. Your dashboard/channel views look connected, so the remaining issue in #628 is better framed as Telegram polling timeout/error noise while the bot is still operational.

The work in #633 / #634 is still useful on our side because it improves diagnosability for real auth/config/startup failures, but it does not fully solve the timeout-spam problem you’re reporting here. We’ll keep #628 framed around that remaining runtime/logging behavior.

[senthazalravi]

how did you paired the telegram