Get Execution - BlobHub

Retrieve details of a specific execution.

POST `/revisions/:id/data/query` (Command: `get_execution`)

Request Body

Parameter	Type	Required	Description
`command`	string	Yes	Must be `get_execution`.
`execution_id`	string	Yes	The ID of the execution.

Response

Parameter	Type	Description
`execution`	object	The execution object, below.

Execution object

Field	Type	Description
`id`	string	Execution id.
`revision_id`	string	The session’s revision.
`session_id`	string	The session this execution belongs to — always its id, even when `target.session` named it by alias.
`status`	string	Execution status.
`workflow`	object	The `workflow` object of the request that created this execution, verbatim, exactly as it arrived.
`definition`	object	What `workflow` resolved to: `{org_id, blob_id, revision_id, id, alias}` — `alias` is `null` if unknown.
`snapshot`	string	`"created"` or `"backfilled"`. Absent when the execution has no snapshot. See The execution snapshot.
`description`	string	The creating request’s `description`. Absent when none was sent.

workflow is what was asked and can go stale — default follows the default revision, and aliases can be renamed. definition is what it resolved to, pinned. See The workflow reference.

Example

{
  "command": "get_execution",
  "execution_id": "exec_001"
}

{
  "status": "success",
  "execution": {
    "id": "exec_001",
    "session_id": "8d41b7e3-5c2a-4f90-a1b6-3e7d9c0f2a15",
    "status": "running",
    "description": "Nightly data processing run",
    "workflow": {"definition": "data-process"},
    "definition": {"org_id": "org_001", "blob_id": "blob_001", "revision_id": "rev_001", "id": "def_001", "alias": "data-process"},
    "snapshot": "created"
  }
}