Documentation Index
Fetch the complete documentation index at: https://docs.blobhub.io/llms.txt
Use this file to discover all available pages before exploring further.
List executions of a specific schedule. Results are sorted by creation time (newest first) and paginated in batches of 10. Executions are fire-and-forget records of past schedule firings.
POST /revisions/:id/data (Command: list_executions)
Request Body
| Parameter | Type | Required | Description |
|---|
engine | string | Yes | Must be scheduler_blobhub. |
command | string | Yes | Must be list_executions. |
schedule_id | string | Yes | Id of the schedule whose executions to list. |
start_execution_id | string | No | Pagination cursor. Pass the last_execution_id from the previous page. |
include_schedule | boolean | No | When true, the response also includes the parent schedule object. |
Response
| Parameter | Type | Description |
|---|
executions | array | Execution objects in descending created_at order (up to 10 per page). |
last_execution_id | string / null | Pagination cursor for the next page, or null if there are no more pages. |
schedule | object | Parent schedule object. Only present when include_schedule is true. |
| Field | Type | Description |
|---|
id | string | Execution id. |
schedule_id | string | Id of the parent schedule. |
created_at | string | ISO 8601 UTC timestamp when the execution was recorded. |
invocation_target_type | string | Target type, currently workflow. |
invocation_target | object | Snapshot of the schedule’s invocation target at the time of firing. |
status | string | success, access_error, or invocation_error. |
result | object | Status-specific result data (e.g. error details or invocation output). |
Example
{
"engine": "scheduler_blobhub",
"command": "list_executions",
"schedule_id": "sched-001"
}
