Monitor created in a paused group becomes stuck in an invalid paused state after resuming the group

[MrNerubian]

📑 I have found these related issues/pull requests

Description:

If a group is paused, and a new monitor is created inside this paused group, then after resuming the group, the newly created monitor enters an inconsistent state.

Observed behavior:

• The new monitor:

  • Appears gray as if it is still paused
  • Shows a Resume button, but the button is not clickable

• The monitor cannot be resumed normally

Workaround:

• Open the monitor’s Edit page
• Change any setting
• Save the monitor
• After saving, the monitor returns to a normal active state

Expected behavior:

• After resuming a paused group, all monitors in the group (including newly created ones) should:

  • Become active correctly
  • Have a functional Resume button if applicable

Impact:

• Creates a broken UI / state inconsistency
• Users may think the monitor is permanently paused or broken

🛡️ Security Policy

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

📝 Description

When a group is in a paused state, creating a new monitor inside that group results in an inconsistent monitor state after the group is resumed.
The newly created monitor appears paused and cannot be resumed through the UI.

👟 Reproduction steps

1. Create a group.
2. Pause the group.
3. While the group is paused, create a new monitor inside the group.
4. Resume the group.
5. Observe the state of the newly created monitor.

👀 Expected behavior

• After resuming a paused group, all monitors in the group (including newly created ones) should:

  • Become active normally
  • Have functional pause/resume controls

😓 Actual Behavior

• The newly created monitor:

  • Appears gray, as if it is still paused
  • Displays a Resume button that is not clickable

• The monitor remains in this broken state until it is edited and saved manually.

🐻 Uptime-Kuma Version

2.0.2

💻 Operating System and Arch

Red Hat Enterprise Linux 64 bit 8.7

🌐 Browser

Google Chrome 143.0.7499.193

🖥️ Deployment Environment

📝 Relevant log output

[aviralgarg05]

I would like to solve the issue, please assign me

[CommanderStorm]

Like most oss projects we don't assign people to issues, since we are all volunteers here.
Running a burocracy is not our goal, so we usually don't assign people to issues ^^

[CommanderStorm]

But I would love your contribution on this