get_data_pipeline_execution_details

DataPipelinesApi.get_data_pipeline_execution_details(executionid, id, role_id, _request_timeout=None, _request_auth=None, _content_type=None, _headers=None, _host_index=0)

Get one data pipeline execution

Returns the execution item. Requires read-only access. RUNNING and STOPPING rows are refreshed from Glue or Bedrock before return. Node Timeout defaults to 2880 for non-start/end nodes. Internal Glue argument keys are stripped.

Parameters:

  • executionid (str) – DataPipelineExecutionId (Glue workflow run id or AI flow execution id). (required)

  • id (str) – DataPipelineId. (required)

  • role_id (str) – Amorphic role ID the request is authorized against. Must be a role the user belongs to. Lambda returns AUTH-1001 (HTTP 403 on v2-dataPipelines, HTTP 400 on v2-downloadLogs) if missing after gateway validation. (required)

  • _request_timeout (int, tuple(int, int), optional) – timeout setting for this request. If one number provided, it will be total request timeout. It can also be a pair (tuple) of (connection, read) timeouts.

  • _request_auth (dict, optional) – set to override the auth_settings for an a single request; this effectively ignores the authentication in the spec for a single request.

  • _content_type (str, Optional) – force content-type for the request.

  • _headers (dict, optional) – set to override the headers for a single request; this effectively ignores the headers in the spec for a single request.

  • _host_index (int, optional) – set to override the host_index for a single request; this effectively ignores the host_index in the spec for a single request.

Return type:

GetDataPipelineExecutionDetailsResponse

Returns:

Returns the result object.

Request and Response Examples

HTTP: GET /data-pipelines/{id}/executions/{executionid}

Success (HTTP 200)

GetDataPipelineExecutionDetailsResponse.

Completed Glue execution

{
  "DataPipelineId": "a1b2c3d4-e5f6-7890-abcd-ef1234567890",
  "DataPipelineExecutionId": "wr_abc123",
  "StartedOn": "2026-08-01 10:00:00",
  "CompletedOn": "2026-08-01 10:12:00",
  "ExecutionStatus": "COMPLETED",
  "Nodes": [
    {
      "ModuleType": "etl_job",
      "NodeName": "enrich_orders",
      "JobRunState": "SUCCEEDED",
      "Timeout": 2880
    }
  ],
  "Graph": {
    "start": {
      "success": [
        "enrich_orders"
      ],
      "failure": []
    },
    "enrich_orders": {
      "success": [
        "end"
      ],
      "failure": []
    },
    "end": {
      "success": [],
      "failure": []
    }
  }
}

Errors

Documented error codes: AUTH-1001, GE-1046, AUTH-1012, GE-1028, GE-1044.

HTTP 400

API Gateway request validation (missing required parameters such as role_id). Lambda InvalidInputException from this function is HTTP 403.

Gateway rejected missing required header

{
  "Message": "Invalid request"
}

HTTP 403

Invalid input or unauthorized. dataPipelines maps InvalidInputException and UnauthorizedUserException to HTTP 403.

Missing role_id after gateway

{
  "Message": "AUTH-1001 - Missing role information in event header"
}

Unknown pipeline or execution id

{
  "Message": "GE-1046 - Invalid DataPipelineId id received - 00000000-0000-0000-0000-000000000000"
}

Insufficient access on the pipeline

{
  "Message": "AUTH-1012 - User: user1 requires at least read-only access on the resource to perform this action."
}

Listing limit greater than 1000

{
  "Message": "GE-1028 - Out of range for items per page, Limit is 1000"
}

HTTP 500

Backend failure (GenericFailureException, InconsistentMetadataException, or unexpected GE-1044).

Unhandled exception

{
  "Message": "GE-1044 - Unexpected error - An unexpected error occurred."
}