Documentation

Runs and results

Reading run history, statuses, screenshots, and AI summaries.

A run is one execution of a monitor. Every run is recorded whether it was scheduled or started with Run Now.

Where to find runs

  • Runs in the navigation shows every run across the workspace, newest first, with counts of total runs, failures, and detected changes. Filter by status, or search.
  • View Runs on a monitor card shows only that monitor's runs.
  • A monitor's detail page (click its name) shows its recent runs and a history timeline.

Statuses

Status Meaning
Passed The check succeeded (workflow), or no meaningful change was found (change monitor).
Failed The workflow check did not succeed, or the page could not be captured.
Change detected A change monitor found a significant difference from the baseline.
Running In progress. Runs usually take a few seconds; media-heavy sites can take longer.

The first run of a change monitor is recorded as passed — it only captures the baseline.

What a run contains

  • Screenshot of the page or region as it was captured. Change runs also keep the before screenshot and a diff image highlighting what moved.
  • Timing — when it started and how long it took.
  • HTTP status and the final URL after any redirects.
  • Summary — for workflow monitors, a plain-language explanation of the outcome; for change monitors, an AI description of what changed, its significance, and category.
  • Failure detail — the technical reason, shown beneath the plain-language explanation.

Manual runs

Run Now on any monitor card runs it immediately. Manual runs count against your allowance like scheduled ones. Manual runs don't send alert emails — only scheduled runs do — so you can test freely without notifying anyone.

A manual run doesn't change the monitor's schedule; the next scheduled run happens when it would have anyway.

Screenshots and retention

Screenshots are stored securely and are only viewable by members of your workspace. They're kept for seven days.

Trigger types

Each run records how it started: scheduled (by the monitoring service on its interval) or manual (Run Now, or a call to the API). This appears in the run detail.