Bug when updating status change if using retries setting with a push monitor #4062

New issue

Open

opened 2026-02-28 03:49:49 -05:00 by deekerman · 0 comments

deekerman commented

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

Owner

Originally created by @Hack3rH0g on GitHub (Mar 31, 2025).

None found.

🛡️ Security Policy

I agree to have read this project Security Policy

Description

I have created a push monitor with "Retries" set to 1. If the monitor goes down (sending out a down notification), enters the pending state, and then goes back up, there is no status change triggering a new notification to go out. In other words, the only notification I get is that the service went down, but there is no second notification that the service is actually running again, forcing me to manually check.

I created a test monitor as an example:

👟 Reproduction steps

Manual reproduction using a push monitor with retires set to 1:

https://{{ uptime-kuma-server }}/api/push/{{ push-monitor-endpoint }}?status=up
https://{{ uptime-kuma-server }}/api/push/{{ push-monitor-endpoint }}?status=down
* wait for the monitor to go into the pending state *
https://{{ uptime-kuma-server }}/api/push/{{ push-monitor-endpoint }}?status=up

👀 Expected behavior

The switch from down to up, even when the monitor goes into the pending state in between, should trigger a status change and send out a new notification.

😓 Actual Behavior

A status change to cause a new notification to be sent out is not registered.

🐻 Uptime-Kuma Version

1.23.16

💻 Operating System and Arch

Ubuntu

🌐 Browser

Firefox

🖥️ Deployment Environment

N/A

📝 Relevant log output

Originally created by @Hack3rH0g on GitHub (Mar 31, 2025). ### 📑 I have found these related issues/pull requests None found. ### 🛡️ Security Policy - [x] I agree to have read this project [Security Policy](https://github.com/louislam/uptime-kuma/security/policy) ### Description I have created a push monitor with "Retries" set to 1. If the monitor goes down (sending out a down notification), enters the pending state, and then goes back up, there is no status change triggering a new notification to go out. In other words, the only notification I get is that the service went down, but there is no second notification that the service is actually running again, forcing me to manually check. I created a test monitor as an example: ![Image](https://github.com/user-attachments/assets/f52d7c57-58d3-4c93-8b5b-a114c271e352) ### 👟 Reproduction steps Manual reproduction using a push monitor with retires set to 1: ``` https://{{ uptime-kuma-server }}/api/push/{{ push-monitor-endpoint }}?status=up https://{{ uptime-kuma-server }}/api/push/{{ push-monitor-endpoint }}?status=down * wait for the monitor to go into the pending state * https://{{ uptime-kuma-server }}/api/push/{{ push-monitor-endpoint }}?status=up ``` ### 👀 Expected behavior The switch from down to up, even when the monitor goes into the pending state in between, should trigger a status change and send out a new notification. ### 😓 Actual Behavior A status change to cause a new notification to be sent out is not registered. ### 🐻 Uptime-Kuma Version 1.23.16 ### 💻 Operating System and Arch Ubuntu ### 🌐 Browser Firefox ### 🖥️ Deployment Environment N/A ### 📝 Relevant log output ```shell ```