get_etl_job_execution_status

EtlJobsApi.get_etl_job_execution_status(executionid, id, role_id, projection_expression=None, lineage_type=None, _request_timeout=None, _request_auth=None, _content_type=None, _headers=None, _host_index=0)

Get job execution details

Returns details for a specific execution from a particular job, including optional Reruns for related re-executions. When OpenLineage is enabled, lineageType can request openlineage or columnlineage details.

Parameters:

  • executionid (str) – Glue JobRun / execution ID to retrieve. (required)

  • id (str) – UUID of the parent ETL job. (required)

  • role_id (str) – Amorphic role ID sent for authorization. Missing this header returns AUTH-1001. (required)

  • projection_expression (str) – Comma-separated attribute names to include on the execution. When omitted, the full execution object is returned. Example: Id,JobRunState,StartedOn,CompletedOn.

  • lineage_type (str) – Request OpenLineage or column lineage when data lineage is enabled for supported Glue versions. Allowed values are openlineage and columnlineage. Any other value returns IPV-1071.

  • _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:

ExecutionStatusResponse

Returns:

Returns the result object.

Request and Response Examples

HTTP: GET /jobs/{id}/executions/{executionid}

Success (HTTP 200)

JobExecution details; Reruns included for root executions. Lineage requests may return Message, PresignedUrl, and FileName instead.

Request / response example

{
  "JobExecution": {
    "Id": "jr_a1b2c3d4e5f6",
    "JobId": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
    "JobName": "sales_etl_daily",
    "JobRunState": "succeeded",
    "JobBookmarkOption": "disable",
    "StartedOn": "2026-08-15 09:00:00",
    "LastModifiedOn": "2026-08-15 09:12:00",
    "CompletedOn": "2026-08-15 09:12:00"
  },
  "Reruns": []
}

Errors

Documented error codes: IPV-1071, GE-1034, GE-1008.

HTTP 400

Invalid lineageType, execution/job mismatch, missing job, or insufficient access.

lineageType is not allowed

{
  "Message": "IPV-1071 - Invalid value of lineageType, allowed values are openlineage, columnlineage"
}

Execution does not belong to the job

{
  "Message": "GE-1034 - Execution ID jr_a1b2c3d4e5f6 does not belong to Job ID 3fa85f64-5717-4562-b3fc-2c963f66afa6"
}

HTTP 500

Uncaught backend failure. Typical Message is “GE-1008 - Could not complete the request. Please try again.”

Request / response example

{
  "Message": "GE-1008 - Could not complete the request. Please try again."
}