Pause controls at every level, and a 7-day history on every form

Pause a form for 1h, 4h, 24h or until you resume; pause a whole site while it's being worked on. Timed pauses resume themselves. Plus a History view of every form's last 7 days of checks.


May 28, 2026 · Formitor

Monitoring needs an off switch that isn’t embarrassing. When a site is mid-redesign, the alert about its rebuilt contact form isn’t signal, it’s noise you caused yourself. But “just ignore alerts from that site for a while” is how real failures slip through.

Pause, scoped and timed

Per form: every form now has a Pause control. Pause for 1h, 4h, 24h, or until you resume. Paused forms aren’t submitted and don’t alert, and timed pauses resume themselves, so protection comes back without you remembering anything.

Per site: each site card has a Pause/Resume button for the working-on-it case. Paused sites show a “Paused” badge and are dimmed, so they never read as healthy.

Honesty on the outside: paused items show as Paused (grey) on shared status pages too, never as a fake green.

The timed pause is the hero here. “Pause for 4 hours” matches how work actually happens: you’re rebuilding the form this afternoon. An untimed pause relies on your memory; a timed one relies on a clock.

The History button

Every form also gained a History view: the last 7 days of synthetic checks, when each passed, its delivery status, how long it took, and the exact error on any failure.

“Is this form flaky or was that a one-off?” used to be a feeling. Now it’s a list. A form that failed once in 14 checks is a blip; one that failed every night at 2 a.m. is a cron job fighting your SMTP relay, and the history makes the pattern visible in seconds.

Catch the failure before the client does.

Free plan: 2 sites, every feature, no card. See what it finds.