starred/uptime-kuma

Fork 0

mirror of https://github.com/louislam/uptime-kuma.git synced 2026-03-02 22:57:00 -05:00

Paused monitor still be monitored #2808

New issue

Closed

opened 2026-02-28 03:07:56 -05:00 by deekerman · 4 comments

deekerman commented

2026-02-28 03:07:56 -05:00

Owner

Originally created by @solracsf on GitHub (Nov 19, 2023).

⚠️ Please verify that this bug has NOT been raised before.

I checked and didn't find similar issue

🛡️ Security Policy

I agree to have read this project Security Policy

Description

When a monitor is paused it still be monitored. It shouldn't.

👟 Reproduction steps

Pause a HTTP monitor (attached to a group, don't know if this is important)
Stop the Webserver
Monitor will be reported as down

👀 Expected behavior

Paused monitor should be...paused.

😓 Actual Behavior

Paused monitor is monitored.

🐻 Uptime-Kuma Version

1.23.4

💻 Operating System and Arch

Ubutnu 22.0.4

🌐 Browser

Brave

🐋 Docker Version

No response

🟩 NodeJS Version

No response

📝 Relevant log output

No response

Originally created by @solracsf on GitHub (Nov 19, 2023). ### ⚠️ Please verify that this bug has NOT been raised before. - [X] I checked and didn't find similar issue ### 🛡️ Security Policy - [X] I agree to have read this project [Security Policy](https://github.com/louislam/uptime-kuma/security/policy) ### Description When a monitor is paused it still be monitored. It shouldn't. ### 👟 Reproduction steps 1. Pause a HTTP monitor (attached to a group, don't know if this is important) 2. Stop the Webserver 3. Monitor will be reported as down ### 👀 Expected behavior Paused monitor should be...paused. ### 😓 Actual Behavior Paused monitor is monitored. ![image](https://github.com/louislam/uptime-kuma/assets/12234510/8d428e82-d02f-4fb9-b660-b2c86b2b7708) ### 🐻 Uptime-Kuma Version 1.23.4 ### 💻 Operating System and Arch Ubutnu 22.0.4 ### 🌐 Browser Brave ### 🐋 Docker Version _No response_ ### 🟩 NodeJS Version _No response_ ### 📝 Relevant log output _No response_

deekerman

2026-02-28 03:07:56 -05:00

closed this issue
added the
bug
label

deekerman commented

2026-02-28 03:08:03 -05:00

Author

Owner

@chakflying commented on GitHub (Nov 19, 2023):

Duplicate of #4028, fixed in #4032, please check version 1.23.6.

@chakflying commented on GitHub (Nov 19, 2023): Duplicate of #4028, fixed in #4032, please check version `1.23.6`.

deekerman commented

2026-02-28 03:08:04 -05:00

Author

Owner

@solracsf commented on GitHub (Nov 20, 2023):

Thanks, but as here, monitor is not resumed (at least, it does not appear as resumed in the GUI, see the button "Resume" in my screenshot), I thought it was not the same issue.

@solracsf commented on GitHub (Nov 20, 2023): Thanks, but as here, monitor is not resumed _(at least, it does not appear as resumed in the GUI, see the button "Resume" in my screenshot)_, I thought it was not the same issue.

deekerman commented

2026-02-28 03:08:04 -05:00

Author

Owner

@chakflying commented on GitHub (Nov 20, 2023):

When I reproduced this, the UI is indeed paused, but the heartbeats continues to get updated, and a refresh of the browser would show the correct status, which is running.

I believe it's related to the way checkMonitors resumes monitors where the status does not get sent to clients.

@chakflying commented on GitHub (Nov 20, 2023): When I reproduced this, the UI is indeed paused, but the heartbeats continues to get updated, and a refresh of the browser would show the correct status, which is running. I believe it's related to the way `checkMonitors` resumes monitors where the status does not get sent to clients.

deekerman commented

2026-02-28 03:08:04 -05:00

Author

Owner

@chakflying commented on GitHub (Nov 24, 2023):

Fixed by #4088.

@chakflying commented on GitHub (Nov 24, 2023): Fixed by #4088.

deekerman referenced this issue

2026-02-28 04:14:06 -05:00

Badges on the status page should default their suffix based on the requested duration #4754