Heartbeat Retry Interval time (seconds) not working #279

Closed
opened 2026-02-28 01:41:13 -05:00 by deekerman · 2 comments
Owner

Originally created by @R0GGER on GitHub (Sep 29, 2021).

Is it a duplicate question?
No.

Describe the bug
I noticed this issue since 1.7.0, but I was unsure it was a configuration error from my side or a bug...
The setting Heartbeat Retry Interval time in seconds is not working.

Screenshot settings:
uk_scr1
When a service goes down, it should retry 3 times every 60 seconds before it sends a notification the service is down.

Screencapture: https://user-images.githubusercontent.com/8298741/135232370-e0cd2714-80dc-4c39-beb8-39badebf913e.mp4
As you can see in this screencapture, all three (3) Heartbeat Retries are send within one (1) minute and the service is marked as down.

Expected behavior
Retries: 3
Heartbeat Retry Interval: 60

Send 3 heartbeats every 60 seconds before the service is marked as down and a notification is sent.

Info
Uptime Kuma Version: 1.7.0.
Using Docker?: Yes
OS: Ubuntu 21.04
Browser: Chrome

Originally created by @R0GGER on GitHub (Sep 29, 2021). **Is it a duplicate question?** No. **Describe the bug** I noticed this issue since 1.7.0, but I was unsure it was a configuration error from my side or a bug... The setting Heartbeat Retry Interval time in seconds is not working. Screenshot settings: ![uk_scr1](https://user-images.githubusercontent.com/8298741/135231959-99276ec2-bffe-4ce3-aa25-7faf7de34552.png) When a service goes down, it should retry 3 times every 60 seconds before it sends a notification the service is down. **Screencapture**: https://user-images.githubusercontent.com/8298741/135232370-e0cd2714-80dc-4c39-beb8-39badebf913e.mp4 As you can see in this screencapture, all three (3) Heartbeat Retries are send within one (1) minute and the service is marked as down. **Expected behavior** Retries: 3 Heartbeat Retry Interval: 60 Send 3 heartbeats every 60 seconds before the service is marked as down and a notification is sent. **Info** Uptime Kuma Version: 1.7.0. Using Docker?: Yes OS: Ubuntu 21.04 Browser: Chrome
deekerman 2026-02-28 01:41:13 -05:00
  • closed this issue
  • added the
    bug
    label
Author
Owner

@louislam commented on GitHub (Sep 29, 2021):

Thanks for the report, I have addressed the problem, will release 1.7.2.

@louislam commented on GitHub (Sep 29, 2021): Thanks for the report, I have addressed the problem, will release 1.7.2.
Author
Owner

@louislam commented on GitHub (Sep 30, 2021):

1.7.3 is available now

@louislam commented on GitHub (Sep 30, 2021): 1.7.3 is available now
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/uptime-kuma#279
No description provided.