mirror of
https://github.com/louislam/uptime-kuma.git
synced 2026-03-02 22:57:00 -05:00
maintenance does not work when ??? #3584
Labels
No labels
A:accessibility
A:api
A:cert-expiry
A:core
A:dashboard
A:deployment
A:documentation
A:domain expiry
A:incidents
A:maintenance
A:metrics
A:monitor
A:notifications
A:reports
A:settings
A:status-page
A:ui/ux
A:user-management
Stale
ai-slop
blocked
blocked-upstream
bug
cannot-reproduce
dependencies
discussion
duplicate
feature-request
feature-request
good first issue
hacktoberfest
help
help wanted
house keeping
invalid
invalid-format
invalid-format
question
releaseblocker 🚨
security
spam
type:enhance-existing
type:new
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/uptime-kuma#3584
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @macaty on GitHub (Sep 2, 2024).
📑 I have found these related issues/pull requests
I have created a daily maintenance schedule from 0:00 to 6:30 and associated all the monitoring items, but I still receive failure alarms, I think the maintenance schedule is experiencing problems, please help me to monitor whether it is a bug or not!
🛡️ Security Policy
Description
No response
👟 Reproduction steps
👀 Expected behavior
You should not be notified of alerts during maintenance
😓 Actual Behavior
You will be notified of alerts during maintenance
🐻 Uptime-Kuma Version
Version: 1.23.13
💻 Operating System and Arch
docker louislam/uptime-kuma alpine 2800880df08e 4 months ago 334MB
🌐 Browser
chrome 128.0.6613.114
🖥️ Deployment Environment
docker AArch64
images louislam/uptime-kuma alpine
📝 Relevant log output
@macaty commented on GitHub (Sep 2, 2024):
server timezone error
@macaty commented on GitHub (Sep 3, 2024):
When I set the correct server time to utc 00:00, the result still doesn't work.
@macaty commented on GitHub (Sep 3, 2024):
@CommanderStorm commented on GitHub (Dec 6, 2025):
no clue how to reproduce this