Overview

Retrieve all execution runs for a specific pipeline. Each run represents a single execution of the pipeline, whether triggered manually or by schedule.

Example

List Pipeline Runs

GET /platform/pipeline/1b33ad2f_33d3_4837_9eeb_83c82c8b909d/pipeline_run

Response (200 OK):

[
  {
    "id": 45,
    "pipeline_run_id": "e7c91a3b_5f2d_4a8e_b1c9_7d3f2e8a4b6c",
    "pipeline_id": "1b33ad2f_33d3_4837_9eeb_83c82c8b909d",
    "last_status": "SUCCESS",
    "created_at": "2024-01-15T10:30:00.000Z",
    "updated_at": "2024-01-15T10:45:23.000Z",
    "trace": null
  },
  {
    "id": 44,
    "pipeline_run_id": "a2b8c4d6_1e3f_5a7b_9c2d_4e6f8a0b2c4d",
    "pipeline_id": "1b33ad2f_33d3_4837_9eeb_83c82c8b909d",
    "last_status": "SUCCESS",
    "created_at": "2024-01-14T06:00:00.000Z",
    "updated_at": "2024-01-14T06:23:45.000Z",
    "trace": null
  },
  {
    "id": 43,
    "pipeline_run_id": "f9d8e7c6_b5a4_3928_1c0d_6e5f4a3b2c1d",
    "pipeline_id": "1b33ad2f_33d3_4837_9eeb_83c82c8b909d",
    "last_status": "FAILED",
    "created_at": "2024-01-13T06:00:00.000Z",
    "updated_at": "2024-01-13T06:15:12.000Z",
    "trace": "Connection timeout to source database"
  }
]

Response Structure

Field	Type	Description
`id`	integer	Internal database ID
`pipeline_run_id`	string	Unique run identifier
`pipeline_id`	string	Parent pipeline identifier
`last_status`	string	Current status of the run
`created_at`	timestamp	When the run started
`updated_at`	timestamp	When the run was last updated
`trace`	string	Error trace or additional information (null if successful)

Run Status Values

Status	Description
`RUNNING`	Execution currently in progress
`SUCCESS`	Execution completed successfully
`FAILED`	Execution failed (check `trace` for details)

Pipeline Run ID Format

The pipeline_run_id follows the same UUID format as pipeline_id:

Example: e7c91a3b_5f2d_4a8e_b1c9_7d3f2e8a4b6c

Error Responses

500 Internal Server Error

{
  "msg": "There was an error retrieving the pipeline_runs.",
  "error": "Database connection error"
}

Use Cases

Monitor Recent Executions

# Get all runs to check execution history
GET /platform/pipeline/1b33ad2f_33d3_4837_9eeb_83c82c8b909d/pipeline_run

Debug Failed Runs

Look for runs with last_status: "FAILED" and check the trace field for error details.

Track Execution Duration

Calculate duration by comparing created_at and updated_at timestamps.

Notes

Runs are returned in chronological order (most recent first may vary)
Returns an empty array [] if no runs exist for the pipeline
For detailed information about a specific run, use GET /platform/pipeline/:pipelineId/pipeline_run/:runId
To retrieve run logs, use GET /platform/pipeline/pipeline_run/:runId/logs