---
title: Incident and alert texts follow your rule and name the reading
description: Some incident texts didn't match the rule that opened them: a CDN error read "Cdn status code reached 400" for a 404, an NTP stratum rule said the server…
canonical: https://watchfor.io/changelog/2026-11-22-incident-texts-follow-the-rule
---

[All updates](/changelog#2026-11-22-incident-texts-follow-the-rule) 🐛 Fixed Incidents Notifications API Nov 22, 2026 · v 13.7.4

# Incident and alert texts follow your rule and name the reading

Some incident texts didn't match the rule that opened them: a CDN error read "Cdn status code reached 400" for a 404, an NTP stratum rule said the server "should stay > 2" next to "value not captured", a 90 % game fill rule called the server full, and HTTP status alerts showed ["2xx", "3xx"]. That was our mistake. Incidents, the API and every notification channel now word the rule the same way, say what the check measured ("HTTP 404", "stratum 3") and give the exact healthy bound ("at most 2").

Share this update

---

Canonical page: https://watchfor.io/changelog/2026-11-22-incident-texts-follow-the-rule · Site guide: https://watchfor.io/llms.txt
