0
Notification lost if service is temporarily unavailable
Source: louislam/uptime-kuma#6046 · opened by @m4rc0d1
π I have found these related issues/pull requests Searched but didn't find any related issue/PR π‘οΈ Security Policy β’ I have read and agree to Uptime Kuma's [Security Policy]( π Description If the notification server is temporarily unreachable/unavailable at the moment of the down/up event, no retries are attempted to send the notification. I have a dual internet connection with a primary and a backup link. If the primary link fails there is a small delay (seconds) before the primary router switches to the backup link and during this short period of time the Telegram server is inaccessible from Uptime Kuma. The down notification of the primary link is never received even if Telegram is reachable just few seconds later. I have not checked if this is just related to Telegram or a more general behavior also affecting other notification channels. π Reproduction steps 1. disable internet connection (or just api.telegram.org) from Uptime Kuma 2. down any monitor confβ¦
No pledges yet. Be the first to back this.
Comments
Similar requests
[Steam game server] should not mark service down if Steam API is down
0 votes · 0 comments
"Lost Connection" Warning on page reload
0 votes · 0 comments
Docker Socket connection is lost during live restore
0 votes · 0 comments
Appearance settings lost after browser cache clear
1 vote · 0 comments
Do not send notifications for `UP` notifications
0 votes · 0 comments
No comments yet.