Not sending `DOWN` -> .. -> `UP` notifications for docker and webhook if transtioning `DOWN` -> `PENDING` -> `UP`, only while `DOWN` -> `UP` #4233

New issue

Open

opened 2026-02-28 03:55:37 -05:00 by deekerman · 1 comment

deekerman commented

2026-02-28 03:55:37 -05:00

Owner

Originally created by @derekoharrow on GitHub (Jul 31, 2025).

N/A

🛡️ Security Policy

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

📝 Description

I've setup a basic monitor of a docker container. I've also setup a notification monitor to call a webhook when monitors go up/down.
The webhook is being called when the monitor goes down, but it's not being called when it goes back up.

Looking at my docker logs for UK, it seems that it detects the container as being down/exited. It then detects it as pending, but it never goes back to "up".

U.K. does now show that the autoheal container is Up, but there's nothing in the log, and no webhook triggered.

Any ideas?

👟 Reproduction steps

See above

👀 Expected behavior

Webhook should be called when container goes back Up.

😓 Actual Behavior

Webhook only being called when Container goes Down.

🐻 Uptime-Kuma Version

Version: 2.0.0-beta.3

💻 Operating System and Arch

Docker on Ubuntu

🌐 Browser

Edge

🖥️ Deployment Environment

Version: 2.0.0-beta.3
Frontend Version: 2.0.0-beta.3

📝 Relevant log output

2025-07-31T16:38:03+01:00 [MONITOR] WARN: Monitor #2 'autoheal': Failing: Container State is exited | Interval: 20 seconds | Type: docker | Down Count: 0 | Resend Interval: 0
2025-07-31T16:38:23+01:00 [MONITOR] WARN: Monitor #2 'autoheal': Pending: starting | Max retries: 0 | Retry: 0 | Retry Interval: 30 seconds | Type: docker
2025-07-31T16:38:53+01:00 [MONITOR] WARN: Monitor #2 'autoheal': Pending: starting | Max retries: 0 | Retry: 0 | Retry Interval: 30 seconds | Type: docker

Originally created by @derekoharrow on GitHub (Jul 31, 2025). ### 📑 I have found these related issues/pull requests N/A ### 🛡️ Security Policy - [x] I have read and agree to Uptime Kuma's [Security Policy](https://github.com/louislam/uptime-kuma/security/policy). ### 📝 Description I've setup a basic monitor of a docker container. I've also setup a notification monitor to call a webhook when monitors go up/down. The webhook is being called when the monitor goes down, but it's not being called when it goes back up. Looking at my docker logs for UK, it seems that it detects the container as being down/exited. It then detects it as pending, but it never goes back to "up". U.K. does now show that the autoheal container is Up, but there's nothing in the log, and no webhook triggered. Any ideas? ### 👟 Reproduction steps See above ### 👀 Expected behavior Webhook should be called when container goes back Up. ### 😓 Actual Behavior Webhook only being called when Container goes Down. ### 🐻 Uptime-Kuma Version Version: 2.0.0-beta.3 ### 💻 Operating System and Arch Docker on Ubuntu ### 🌐 Browser Edge ### 🖥️ Deployment Environment Version: 2.0.0-beta.3 Frontend Version: 2.0.0-beta.3 ### 📝 Relevant log output ```bash session 2025-07-31T16:38:03+01:00 [MONITOR] WARN: Monitor #2 'autoheal': Failing: Container State is exited | Interval: 20 seconds | Type: docker | Down Count: 0 | Resend Interval: 0 2025-07-31T16:38:23+01:00 [MONITOR] WARN: Monitor #2 'autoheal': Pending: starting | Max retries: 0 | Retry: 0 | Retry Interval: 30 seconds | Type: docker 2025-07-31T16:38:53+01:00 [MONITOR] WARN: Monitor #2 'autoheal': Pending: starting | Max retries: 0 | Retry: 0 | Retry Interval: 30 seconds | Type: docker ```