Skip to main content
Every monitored URL has a health status that reflects its current state relative to the baseline. Understanding how statuses work helps you know when an alert is expected, and when something needs attention.

​
Status definitions

​
Typical status flow

A healthy URL moves through statuses in this order:
Here’s what happens at each step: 1. URL added — Awaiting Verification The system records the baseline and waits for the next scheduled poll. 2. Poll matches baseline — OK Each time the page is polled and matches the baseline, the status stays OK. 3. Poll doesn’t match baseline — Warning The page has changed from the baseline. Rather than alerting immediately, WebOrion waits and checks again in 5 minutes to avoid false alerts from transient changes. 4. Second check still doesn’t match — Continuous Monitoring The change is confirmed. An alert is sent. WebOrion continues polling, now comparing each result against the previous alert state rather than the original baseline — so any further changes also trigger alerts. 5. Page returns to baseline — back to OK At any point, if the page matches the original baseline again (either because the change was reverted, or the page was re-baselined), the status returns to OK.

​
What Continuous Monitoring does to alert frequency

With Continuous Monitoring on (default), every new change detected while in Continuous Monitoring state triggers a new alert. This gives you a full audit trail of every successive change. With Continuous Monitoring off, WebOrion continues to poll the page silently on schedule but will not send any further alerts. It will only return to OK once the page matches the baseline again. To configure Continuous Monitoring, see What WebOrion Monitors.