📑 I have found these related issues/pull requests

I have checked, but couldn’t find anything similar.

🛡️ Security Policy

• I have read and agree to Uptime Kuma's Security Policy.

📝 Description

When a monitor is paused and the heartbeats are subsequently deleted, the monitor automatically starts again. This behavior is unexpected.

👟 Reproduction steps

1. Create a monitor, for example an HTTP(s) monitor for google.com that sends a request every 20 seconds.
2. Wait until several heartbeats have been recorded.
3. Pause the monitor.
   3.1 A toast notification confirms that the monitor is paused.
4. Delete the heartbeats.
   4.1 A toast notification confirms that the monitor status is [Up] 200 - OK.
5. Refresh the page. You will see that the monitor has automatically started again.

Result: The heartbeats are successfully deleted, but the monitor automatically restarts.

👀 Expected behavior

The monitor should remain paused after the heartbeats are deleted.

😓 Actual Behavior

The monitor restarts when the heartbeats are deleted and does not remain paused.

🐻 Uptime-Kuma Version

2.1.0

💻 Operating System and Arch

Ubuntu 24.04.3 LTS (GNU/Linux 6.8.0-94-generic x86_64)

🌐 Browser

Brave 1.86.148 - Chromium: 144.0.7559.133 (Official Build) (64-bit)

🖥️ Deployment Environment

• Runtime Environment:
  • Docker: Version 26.1.0 (Build 9714adc)
  • Docker Compose: Version 2.26.1
  • Portainer (BE): Version 2.33.6 (LTS: Yes)
  • MariaDB: Version 12.1.2 (LTS: Yes)
• Database:
  • MariaDB: External
• Database Storage:
  • Filesystem:
    • Linux: ext4
  • Storage Medium: SSD
• Uptime Kuma Setup:
  • Number of monitors: 99

📝 Relevant log output

No relevant log output for this issue.