Monitors
List runs
List a monitor’s runs with GET /v1/monitors//runs, newest first, each with the results it returned.
GET
List a monitor's runs
List a monitor’s runs, newest first. Each completed run carries the pages it returned in
results.
When to use it
Read the run history to catch up on digests you missed, or to find failed runs: a failed run hasstatus failed and says why in error. Its pages aren’t lost. They come with the next run that succeeds. Pages and pagination work as in List monitors: pass next_cursor as cursor for the next page.
A run returns at most search.max_results pages. For every page the monitor accepted, including those past that cap, use List results.
SDK, CLI and MCP
The SDK methods need SDK 0.2.0 or later. See SDKs → Monitors and CLI → Monitors.
Related operations
- Get a run reads one run by
run_id. - Run a monitor now starts a run outside the schedule.
- What a run returns explains which pages a run includes.