A schedule's recent firings
list_schedule_runsRetrieve recent firings of one schedule, newest first, with start time, duration, success, and HTTP status to confirm whether the cron ran before troubleshooting the schedule, block, or version.
Instructions
Every recent firing of one schedule, newest first: when it started, how long it took, whether it succeeded, and what HTTP status the execution returned.
THIS is how you answer "did the cron actually run". list_schedules carries only the LAST outcome, and block execution logs exist only for blocks with logging switched on — so a healthy schedule with logging off leaves no trace anywhere else and looks exactly like one that never fired. Check here before touching the cron, the block or the version: the usual finding is that it ran fine every time and the real problem is elsewhere (start with canvasAheadOfPin on list_schedules).
httpStatus separates the failures a user can act on: 429 is a quota they can raise, 503 is the platform's problem, 500 is their code.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"triggerId": "<triggerId>"
},
"name": "list_schedule_runs"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | How many firings to return, newest first. Default 50. | |
| triggerId | Yes |