Troubleshoot PointWarden execution
Start from persistent Pending, stale or missing evidence, reduced Coverage, No Data, or an inactive Monitor without treating execution gaps as Endpoint failure.
Missing Scheduled Check evidence lowers Coverage and can lead to No Data; it never counts as a Failing Check or Endpoint unavailability.
Pending persists
Pending means an active Monitor has no Scheduled Check evidence for its current Monitor Revision. Confirm that the Monitor was created or resumed as Active and that you are viewing the current Revision. An immediate Scheduled Check is due after creation, resumption, or an availability-affecting edit.
If no evidence appears, do not infer that the Endpoint failed. Compare the lifecycle with Modify, pause, resume, and delete a Monitor and the expected initial state in Create a Monitor.
A freshness warning appears
One missing expected Scheduled Check produces a freshness warning. Inspect the latest Check Evidence timestamp and Monitor Revision, then ask whether PointWarden produced evidence for the expected Check. The warning describes evidence freshness, not a Failing Endpoint response.
Coverage falls
Coverage compares expected regular Scheduled Checks with the Check Evidence PointWarden produced. Skipped, obsolete, internally failed, missing, or unfinished work lowers Coverage without adding a Failing Check to Availability.
Read Availability and Coverage together. High Availability with reduced Coverage means the evidence PointWarden did produce was mostly Passing, but the observation has gaps.
No Data appears
After two consecutive expected Scheduled Checks produce no Check Evidence, the Monitor becomes No Data and PointWarden makes no current Availability claim. No Data does not turn missing evidence into Endpoint unavailability and does not close an open Incident.
The Monitor is inactive
A Paused Monitor intentionally produces no Scheduled Checks and makes no current Availability claim. A Deleted Monitor cannot run Checks. Resuming a Paused Monitor makes it Active and Pending while the immediate Scheduled Check produces evidence for its current Revision.
A Manual Check passes, but Availability does not change
A passing Manual Check is diagnostic evidence only. It does not change Availability, clear No Data, advance confirmation state, resolve an Incident, update Availability Rollups, or create Notification Events.
Wait for Scheduled Check evidence and follow the Incident and Recovery confirmation sequence. Use the Test Requests, Manual Checks, and Scheduled Checks comparison to confirm which evidence can change product state.