List Schedule Runs

Scheduler prerequisites

Configure an AgentOS-level database with schedule methods. The example scheduler server uses SQLite. Database-backed schedule CRUD is available without starting the scheduler; execution requires scheduler=True, a running application lifespan and a scheduler_base_url matching the server's address.

Owners come from authenticated identity. Configured authorization uses schedules:read, schedules:write and schedules:delete. Creating, repointing, enabling or triggering a run schedule also requires permission to run its target. Non-run targets require admin permission when that authorization is enforced. An inaccessible record can return 404; insufficient permission returns 403.

Results contain schedule execution records in data with pagination meta. Keep each record's id for the schedule-run detail endpoint; its component run_id and session_id identify the underlying execution separately.

curl --request GET 'https://example.com/schedules/string/runs'

{  "data": [    {      "id": "string",      "schedule_id": "string",      "user_id": "string",      "attempt": 0,      "triggered_at": 0,      "completed_at": 0,      "status": "string",      "status_code": 0,      "run_id": "string",      "session_id": "string",      "error": "string",      "input": {},      "output": {},      "requirements": [        {}      ],      "created_at": 0    }  ],  "meta": {    "page": 0,    "limit": 20,    "total_pages": 0,    "total_count": 0,    "search_time_ms": 0  }}

{  "detail": [    {      "loc": [        "string"      ],      "msg": "string",      "type": "string",      "input": null,      "ctx": {}    }  ]}