Test Requests, Manual Checks, and Scheduled Checks

Compare diagnostic Test Requests and Manual Checks with the Scheduled Checks that can change PointWarden state.

Comparison

Every Check observes an Endpoint, but only Scheduled Check evidence can change PointWarden's current Availability or confirmation state.

ObservationWhen and why it runsWhat it may change
Test RequestBefore saving, an Owner or Admin tests the draft request configuration and receives immediate diagnostic evidence.Nothing. It does not save the Monitor or change Availability, confirmation state, Incidents, Availability Rollups, or notifications.
Manual CheckAfter saving, any Workspace Member runs an immediate diagnostic Check for the current Monitor Revision.Nothing beyond its own evidence. It does not change Availability, confirmation state, Incidents, Availability Rollups, or notifications.
Scheduled CheckPointWarden runs regular Checks on the configured interval and short confirmation Checks after evidence begins an Incident or Recovery sequence.It may change Availability or confirmation state. Confirmation can open an Incident or confirm Recovery, which creates the related Notification Event.

Availability Rollups and events

Manual Checks never contribute to Availability Rollups and never create notifications.

Executed regular Scheduled Checks contribute to Availability Rollups. They can begin a confirmation sequence, but the first Failing or Passing Check does not create a Notification Event.

Confirmation Checks may open an Incident or confirm Recovery and make the related Notification Event eligible for delivery, but they never contribute to Availability Rollups.

Read the evidence

Use Availability and Coverage to interpret regular evidence, then follow the Incident and Recovery confirmation sequence. If a passing Manual Check appears to disagree with current Availability, review why Manual Check evidence does not change product state. Return to Create a Monitor when you need the setup procedure.