List Schedule Runs

GET /schedules/{schedule_id}/runs

What this schedule has produced, newest first.

Two calls and not one, on purpose. GET /runs is the one place run filtering lives, so the page comes from there — it grew a trigger_ref filter and nothing else; what this handler adds is the 404. Without it, a schedule id from another tenant would answer with an empty page, and “this schedule has never fired” is a very different sentence from “this schedule is not yours”.

Role floor

Requires viewer or above. The floor is a minimum, not a grant: scope filtering still applies on top of it, and a resource in another tenant answers 404 rather than 403.

Parameters

Name	In	Type		Notes
schedule_id	path	string (uuid)	required	—
limit	query	integer	optional	Default 50. min 1 max 200
cursor	query	string | null	optional	—
offset	query	integer | null	optional	min 0

Responses

Status	Description	Body
200	Successful Response	Page_RunView_
422	Validation Error	HTTPValidationError

Only the success paths are declared

Any operation may also answer any status in the error catalogue, and every failure body is the platform envelope — including the 422 this document types as HTTPValidationError.

Example

curl -X GET https://your-deployment.example.com/schedules/{schedule_id}/runs \
  -H "Authorization: Bearer $COBRE_TOKEN"

Response — Page_RunView_

Field	Type		Notes
items	RunView[]	required	—
next_cursor	string | null	optional	—
total	integer | null	optional	—