---
title: Monitor config is validated for its type, everywhere
description: The API accepted a misspelled method, a text timeout or a nonsense cron expression and stored it, so the check quietly did something else — an hourly schedule…
canonical: https://watchfor.io/changelog/2026-09-05-api-config-validation
---

[All updates](/changelog/page/5#2026-09-05-api-config-validation) 🐛 Fixed Sep 5, 2026 · v 6.8.1

# Monitor config is validated for its type, everywhere

The API accepted a misspelled method, a text timeout or a nonsense cron expression and stored it, so the check quietly did something else — an hourly schedule instead of your cron line, say. Config is now checked against the monitor type on every create and update, from the dashboard, the API and MCP alike: a bad value is refused with the key named, unused keys are dropped, cron expressions and timezones must be valid, a rule cannot require more failing locations than the monitor has, and private or internal targets are refused. Config that implies an alert rule now creates that rule too.

Share this update

---

Canonical page: https://watchfor.io/changelog/2026-09-05-api-config-validation · Site guide: https://watchfor.io/llms.txt