mirror of
https://github.com/louislam/uptime-kuma.git
synced 2026-03-02 22:57:00 -05:00
Heartbeat Retry Interval time (seconds) not working #279
Labels
No labels
A:accessibility
A:api
A:cert-expiry
A:core
A:dashboard
A:deployment
A:documentation
A:domain expiry
A:incidents
A:maintenance
A:metrics
A:monitor
A:notifications
A:reports
A:settings
A:status-page
A:ui/ux
A:user-management
Stale
ai-slop
blocked
blocked-upstream
bug
cannot-reproduce
dependencies
discussion
duplicate
feature-request
feature-request
good first issue
hacktoberfest
help
help wanted
house keeping
invalid
invalid-format
invalid-format
question
releaseblocker 🚨
security
spam
type:enhance-existing
type:new
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/uptime-kuma#279
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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:

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
@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 30, 2021):
1.7.3 is available now