Summary
After network connectivity was lost for a couple of hours, the Telegram gateway stopped reconnecting and never recovered on its own. Restarting the gateway was required to restore connectivity.
Reproduction
- Start the gateway with Telegram configured and connected.
- Simulate a prolonged infrastructure outage, for example by disabling networking or causing repeated DNS failures for a few hours.
- Wait for the reconnect loop to exhaust repeated retryable failures.
- Restore network connectivity.
Expected Behavior
The gateway should keep retrying retryable reconnect failures with backoff until connectivity returns or the adapter reports a non-retryable error.
Actual Behavior
The reconnect watcher gives up after repeated retryable failures, so the Telegram adapter remains disconnected permanently until the gateway is restarted.
Notes
This appears to affect transient infrastructure failures such as DNS resolution problems. The failure should remain queued for reconnect instead of being dropped after a fixed attempt limit.
Summary
After network connectivity was lost for a couple of hours, the Telegram gateway stopped reconnecting and never recovered on its own. Restarting the gateway was required to restore connectivity.
Reproduction
Expected Behavior
The gateway should keep retrying retryable reconnect failures with backoff until connectivity returns or the adapter reports a non-retryable error.
Actual Behavior
The reconnect watcher gives up after repeated retryable failures, so the Telegram adapter remains disconnected permanently until the gateway is restarted.
Notes
This appears to affect transient infrastructure failures such as DNS resolution problems. The failure should remain queued for reconnect instead of being dropped after a fixed attempt limit.