Open hanyuwei70 opened 1 year ago
I had the same issue, no matter what I tried or which recurring type I used.
As soon as I left the "Effected Date Range" empty (which is now Optional) it worked again. Seems like a bug somewhere in there.
I had the same issue, no matter what I tried or which recurring type I used.
As soon as I left the "Effected Date Range" empty (which is now Optional) it worked again. Seems like a bug somewhere in there.
Works for me! Thanks.
I have the exact same issue for last few weeks, removed "Effected Date Range" and scheduled maintenance is now successfully running. Thanks!
Same here, can confirm that this workaround fixed it for me, thanks!
I can confirm that also worked for me. I was pulling my hair out trying to figure out why the maintenance mode was not kicking in at scheduled time.
ā ļø Please verify that this bug has NOT been raised before.
š”ļø Security Policy
Description
I have set up one maintenance using these settings.
but when maintenance window should work, it still send me alerts.
This issue happened after I updated from 1.21.0 to 1.21.2 (not very sure)
š Reproduction steps
Described above
š Expected behavior
Not raise any alerts
š Actual Behavior
Raise alters even in maintenance window.
š» Uptime-Kuma Version
1.21.2
š» Operating System and Arch
Arch Linux
š Browser
Edge
š Docker Version
23.0.1
š© NodeJS Version
No response
š Relevant log output