louislam/uptime-kuma

[WeCom] Using multiple notifications will cause omissions

Open

#4223 opened on Dec 12, 2023

View on GitHub
 (4 comments) (0 reactions) (0 assignees)JavaScript (86,760 stars) (7,844 forks)batch import
A:notificationsbughelp wantedtype:enhance-existing

Description

⚠️ Please verify that this bug has NOT been raised before.

  • I checked and didn't find similar issue

🛡️ Security Policy

Description

I created 2 different notification WeComs (two different KEYs) for the same website monitoring because different users need to be notified. The problem is that the notification information of the second notification WeCom created is often missing, but the first notification WeCom can receive the notification normally. I tried turning off the first notification, but now the first one can still send reminders normally, but the second one basically cannot send reminders.

need your help

grateful!

👟 Reproduction steps

Create 2 notification WeComs notification rules

👀 Expected behavior

For the same website monitoring, I chose to allow these two rules to be notified at the same time.

😓 Actual Behavior

Only the wecom notification created first can be notified normally, and the second wecom notification cannot work properly. (The second is that you can receive a test message to confirm that there is no problem with the configuration)

🐻 Uptime-Kuma Version

1.23.7

💻 Operating System and Arch

CentOS 7.9.2009 x86_64

🌐 Browser

chrome 119.0.6045.161

🐋 Docker Version

119.0.6045.161

🟩 NodeJS Version

No response

📝 Relevant log output

No response

Contributor guide

Tech stack
javascriptnodejs
Domain
backend
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Familiarity with uptime kumaNode.js debugging basics
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60
Research direction
Investigate the WeCom notification provider implementation in server/notification.js (or similar). Look for race conditions or shared state that could cause only the first notification to succeed. Check the notification dispatch loop and ensure that each provider instance uses its own configuration. Reproduce by setting up two WeCom notifications with different keys and monitoring logs for error messages.