Wait For Execution
Wait for execution to complete (LEGACY - CLI only).
WARNING: This endpoint blocks the HTTP connection until completion. NOT recommended for:
- Frontend applications (use GET /events SSE instead)
- Load-balanced environments
- Long-running executions
Use cases where this is acceptable:
- CLI tools with —wait flag
- CI/CD scripts with timeout
- Simple synchronous integrations
For reactive monitoring, use GET /executions/{id}/events instead.
Args: execution_id: Execution UUID to wait for request: Wait request with timeout waiter: Execution waiter (injected) service: Execution service for stats (injected)
Returns: Wait result with completion status and final statistics
Raises: HTTPException: 404 if execution not found, 503 if waiter unavailable
Parameters
Section titled “ Parameters ”Path Parameters
Section titled “Path Parameters ”Request Body required
Section titled “Request Body required ”Request to wait for execution completion.
object
Maximum time to wait in seconds (1-3600)
Responses
Section titled “ Responses ”Successful Response
Response from waiting for execution completion.
object
Whether execution completed (vs timeout)
Execution UUID
How long the wait took in milliseconds
Execution statistics (derived from lineage).
object
Execution UUID
Total messages processed
Successfully completed messages
Failed messages
Messages still processing
Completion success rate
Resource not found
Standard error response matching FastAPI HTTPException format.
This model is used in OpenAPI response declarations for 4xx/5xx errors.
The detail field matches FastAPI’s HTTPException structure.
Validation Error
object
object
object
Execution waiter not available
Standard error response matching FastAPI HTTPException format.
This model is used in OpenAPI response declarations for 4xx/5xx errors.
The detail field matches FastAPI’s HTTPException structure.