π I have found these related issues/pull requests
unable to find any
π‘οΈ Security Policy
π Description
Thank you for uptime kuma!
If I create a push monitor type and set the heartbeat interval to 129600 seconds, and after that go into the details of this new monitor, I see the text: "Check every 129600 seconds ( 12 hours)". This is not correct. 129600 seconds equals 36 hours.
π Reproduction steps
create a push monitor type and set the heartbeat interval to 129600 seconds
π Expected behavior
"Check every 129600 seconds (1 day and 12 hours)"
π Actual Behavior
"Check every 129600 seconds ( 12 hours)"
π» Uptime-Kuma Version
2.0.2
π» Operating System and Arch
Linux rcl1.2oren.nl 6.8.0-1041-oracle #42~22.04.1-Ubuntu SMP Fri Dec 5 16:59:35 UTC 2025 aarch64 aarch64 aarch64 GNU/Linux
π Browser
Brave 1.85.116 (Official Build) (64-bit) Chromium: 143.0.7499.110
π₯οΈ Deployment Environment
- Runtime Environment:
Docker version 29.1.3, build f52814d
π Relevant log output
π I have found these related issues/pull requests
unable to find any
π‘οΈ Security Policy
π Description
Thank you for uptime kuma!
If I create a push monitor type and set the heartbeat interval to 129600 seconds, and after that go into the details of this new monitor, I see the text: "Check every 129600 seconds ( 12 hours)". This is not correct. 129600 seconds equals 36 hours.
π Reproduction steps
create a push monitor type and set the heartbeat interval to 129600 seconds
π Expected behavior
"Check every 129600 seconds (1 day and 12 hours)"
π Actual Behavior
"Check every 129600 seconds ( 12 hours)"
π» Uptime-Kuma Version
2.0.2
π» Operating System and Arch
Linux rcl1.2oren.nl 6.8.0-1041-oracle #42~22.04.1-Ubuntu SMP Fri Dec 5 16:59:35 UTC 2025 aarch64 aarch64 aarch64 GNU/Linux
π Browser
Brave 1.85.116 (Official Build) (64-bit) Chromium: 143.0.7499.110
π₯οΈ Deployment Environment
Docker version 29.1.3, build f52814d
π Relevant log output