Docs

How Alerts Work

Alerts are created when check status changes indicate a new issue. FormPulse avoids creating duplicate unresolved alerts of the same type for the same form.

• Health: Form missing or page fetch failed (high severity).
• Activity: no confirmations within threshold (warning).
• Learning: no confirmations during learning window (warning).
• Recovery: form recovered after previous failure (informational).

Alert Sensitivity

Sensitivity controls learning-mode threshold calculation through a multiplier:

• Paranoid: 1.0x (alerts sooner).
• Default: 1.5x (balanced).
• Relaxed: 2.0x (alerts later, fewer false positives).

Site-level sensitivity overrides organization-level sensitivity.

Silence Thresholds

The activity threshold is measured in minutes. If confirmations are absent beyond that period, activity warnings appear. You can set a custom threshold manually or let learning mode set one automatically.

“Issue Fixed” vs “No Issues Found”

• Issue Fixed: resolves the alert only (marks resolved_at).
• No Issues Found (for activity alerts): resolves and optionally extends threshold so lower-volume periods do not trigger repeated alerts.
• For learning alerts, you now have two actions: Extend Existing Window (adds 14 or 30 days on top of current learning), or Restart Learning (restarts from now for 7, 14, or 30 days).
• Mark as Unresolved clears resolved_at and reopens the alert.

Tip for testing: use an organization-level whitelisted test email so test submissions do not distort learning/activity signals.

Alerts & Resolution Summary

Turn on the optional summary digest to receive a weekly/bi-weekly/monthly email that summarizes how many forms are currently good, have warnings, are broken, or are in learning mode.

• Good – checks passing with alerts resolved.
• Warning – learning or activity warnings still needing review.
• Broken – health failures that remain unresolved.
• Learning – forms still building a baseline.

It respects the “Default Alert Email Addresses” and can be disabled or overridden per site in Settings, so the right team members always receive the digest.

Staying Notified

We keep an alert open until someone resolves it, and we never create duplicate unresolved alerts for the same issue. If the form keeps failing, you will receive another alert email every time the failing check runs so the incident stays visible in your inbox.

The Form detail page (and the Recent Alerts list) always shows the current status (healthy, warning or broken) even if the alert notification was missed.

If you still don’t notice an email alert, the activity/health history on the dashboard and the analytics page provide another signal that the form has been failing repeatedly, so the issue remains surfaced until someone acknowledges it.

Alerts are kept for around 60 days before being deleted, so the alert list stays current without keeping stale incidents.