Skip to main content
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

ParameterTypeRequiredDescription
enginestringYesMust be scheduler_blobhub.
commandstringYesMust be list_executions.
schedule_idstringYesId of the schedule whose executions to list.
start_execution_idstringNoPagination cursor. Pass the last_execution_id from the previous page.
include_schedulebooleanNoWhen true, the response also includes the parent schedule object.

​
Response

ParameterTypeDescription
executionsarrayExecution objects in descending created_at order (up to 10 per page).
last_execution_idstring / nullPagination cursor for the next page, or null if there are no more pages.
scheduleobjectParent schedule object. Only present when include_schedule is true.
Each execution object has the following shape:
FieldTypeDescription
idstringExecution id.
schedule_idstringId of the parent schedule.
created_atstringISO 8601 UTC timestamp when the execution was recorded.
invocation_target_typestringTarget type, currently workflow.
invocation_targetobjectSnapshot of the schedule’s invocation target at the time of firing.
statusstringsuccess, access_error, or invocation_error.
resultobjectStatus-specific result data (e.g. error details or invocation output).

​
Example

{
  "engine": "scheduler_blobhub",
  "command": "list_executions",
  "schedule_id": "sched-001"
}