---
title: System alert rules can't be turned into a different rule through the API
description: Through the API you could rewrite a monitor's built-in Availability Check into a rule on another metric. The monitor then had no Up/Down rule at all, while…
canonical: https://watchfor.io/changelog/2026-11-22-system-rules-keep-what-they-watch
---

[All updates](/changelog#2026-11-22-system-rules-keep-what-they-watch) 🐛 Fixed Alerting API Nov 22, 2026 · v 13.7.2

# System alert rules can't be turned into a different rule through the API

Through the API you could rewrite a monitor's built-in Availability Check into a rule on another metric. The monitor then had no Up/Down rule at all, while the rule still read "Availability Check" and couldn't be deleted. System rules now keep what they watch: their thresholds, severity, confirmation, contact group and name stay editable, and changing what they measure is refused with a message that says why. For a new condition, add a custom rule.

## What was wrong

PATCH /v1/monitors/{id}/alert-rules/{ruleId} (and update_alert_rule over MCP) accepted any metric , operator or value on a system rule. success == false could become success != false (an alert on every healthy check) or game.players == 0 , and a type default such as Unexpected Status Code could become a response-time rule.

## What changed

- The Availability Check keeps its condition. Rename it, switch it off, or change its confirmation, severity or contact group.

- A type default keeps its metric and stays on its Alerting card. Thresholds can change, and so can the status-code rule's "up when it matches / down when it matches" switch.

- Anything else answers 400 invalid_request naming the rule. Nothing is saved.

- The Alerting tab works as before. Custom rules are unchanged.

Share this update

---

Canonical page: https://watchfor.io/changelog/2026-11-22-system-rules-keep-what-they-watch · Site guide: https://watchfor.io/llms.txt
