starred/uptime-kuma

Fork 0

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

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

New issue

Open

opened 2026-02-28 04:09:40 -05:00 by deekerman · 3 comments

deekerman commented

2026-02-28 04:09:40 -05:00

Owner

Originally created by @MrNerubian on GitHub (Jan 21, 2026).

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

Create a group.
Pause the group.
While the group is paused, create a new monitor inside the group.
Resume the group.
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

Originally created by @MrNerubian on GitHub (Jan 21, 2026). ### 📑 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 - [x] I have read and agree to Uptime Kuma's [Security Policy](https://github.com/louislam/uptime-kuma/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 ```bash session ```

deekerman added the

bug

label

2026-02-28 04:09:40 -05:00

deekerman commented

2026-02-28 04:09:43 -05:00

Author

Owner

@aviralgarg05 commented on GitHub (Jan 24, 2026):

I would like to solve the issue, please assign me

@aviralgarg05 commented on GitHub (Jan 24, 2026): I would like to solve the issue, please assign me

deekerman commented

2026-02-28 04:09:45 -05:00

Author

Owner

@CommanderStorm commented on GitHub (Jan 26, 2026):

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 commented on GitHub (Jan 26, 2026): 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 ^^

deekerman commented

2026-02-28 04:09:45 -05:00

Author

Owner

@CommanderStorm commented on GitHub (Jan 26, 2026):

But I would love your contribution on this

@CommanderStorm commented on GitHub (Jan 26, 2026): But I would love your contribution on this