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/query (Command: list_executions)

Request Body

Response

Each execution object has the following shape:

Errors

A caller cannot tell these two 403 cases apart — a schedule that does not exist and one that is not reachable both answer forbidden. Sessions already work this way; see Close Session.

Example