---
title: One failed check, one incident
description: A check that failed one step often opened two or three critical incidents at once, for example "server rejected the credentials" plus "probe failed" on an FTP…
canonical: https://watchfor.io/changelog/2026-11-22-one-incident-per-failed-check
---

[All updates](/changelog#2026-11-22-one-incident-per-failed-check) 🐛 Fixed Nov 22, 2026 · v 13.8.1

# One failed check, one incident

A check that failed one step often opened two or three critical incidents at once, for example "server rejected the credentials" plus "probe failed" on an FTP monitor with a wrong password, each with its own notification. A failed check now opens one incident, named after the step that failed. And a WebSocket "Response Must Match" failure no longer also opens "High Total Time" for waiting out the timeout.

Share this update

---

Canonical page: https://watchfor.io/changelog/2026-11-22-one-incident-per-failed-check · Site guide: https://watchfor.io/llms.txt
