TheDocumentation Index
Fetch the complete documentation index at: https://docs.iblueprint.ai/llms.txt
Use this file to discover all available pages before exploring further.
execution.getExecutionStatus procedure reads the current state of a blueprint execution from the database. Poll this endpoint after triggering an async execution with execution.executeBlueprintWithLogging to track progress and detect completion or failure. The progress field (0–100) and completedSteps count update as nodes finish, giving you a live view into long-running workflows.
Request
Procedure type: query (HTTPGET)
Endpoint:
Parameters
A URL-encoded JSON object with a
json key containing the parameter below.The execution ID returned by
blueprint.execute or execution.executeBlueprintWithLogging.Response
The execution ID.
Current execution status. One of:
running— actively processing nodescompleted— all nodes finished successfullyfailed— one or more nodes failed and execution stoppedpaused— execution is paused (e.g. awaiting human-in-the-loop input)not_found— no execution record exists for this ID
Integer percentage (0–100) of nodes completed.
ISO 8601 timestamp when execution began.
ISO 8601 timestamp when execution finished.
null if still running.Total number of nodes in this blueprint run.
Number of nodes that have finished successfully.
Number of nodes that failed.
Array of step-level execution records, each describing an individual node run.
Array of log entries produced during execution.
ID of the node currently executing.
undefined if no node is actively running.Present when
status is paused and the blueprint is waiting for user input. Contains details about what input is required.Polling pattern
Poll the status endpoint at a regular interval untilstatus is completed or failed. A 2–5 second interval is appropriate for most blueprints.
