Understanding Pipeline Status
A pipeline execution contains multiple nodes, each representing either:- Query Execution: A query that’s part of the pipeline
- Materialized View Refresh: A materialized view that’s refreshed as part of the pipeline
Pipeline States
The overall pipeline can be in one of the following states:pending: Pipeline execution has been queued but not yet startedexecuting: Pipeline is currently runningcompleted: All nodes in the pipeline have completed successfully
Node Status
Each node in the pipeline includes:node_id: Unique identifier for the nodestatus: Current state of the node executionquery_execution_statusormaterialized_view_refresh_status: Detailed status information
Response Structure
The 200 response includes:status: Overall pipeline execution status (pending, executing, or completed)node_executions: Array of individual node executions with their status and results
Example Usage
Monitoring Pipeline Progress
You can use this endpoint to:- Track which nodes have completed and which are still running
- Identify any nodes that have failed
- Retrieve execution IDs for individual queries to fetch their results
- Monitor overall pipeline health
Once a pipeline execution completes, you can retrieve the results of individual queries using their respective execution IDs from the node status.