# Retrieve an Execution by ID.

Endpoint: GET /executions/{executionId}
Version: 3.23.0
Security: ApiKeyAuth

## Security:

  - `ApiKeyAuth` (unknown)
    apiKey in header Authorization

## Path parameters:

  - `executionId` (string, required)
    The ID of the Execution.

## Response 200:

  - `200` (unknown)
    OK

## Response 200 fields (application/json):

  - `id` (string)
    The Execution entity ID.
    Example: 414ed52c-fa89-455d-9fb9-9c2fa5115f80

  - `engine_id` (string)
    The ID of the engine where this execution ran.
    Example: 1

  - `hyperscale_instance_id` (string)

  - `engine_name` (string)
    The name of the engine where this execution ran.
    Example: prod01

  - `masking_job_id` (string)
    The ID of the masking job that is being executed.
    Example: 2

  - `masking_job_name` (string)
    The name of the masking job that is being executed.
    Example: finance-masking-job

  - `source_connector_id` (string)
    The ID of the source connector. This field is only used for multi-tenant jobs that are also on-the-fly.
    Example: 1-DATABASE-2

  - `target_connector_id` (string)
    The ID of the target connector. This field is only used for multi-tenant jobs.
    Example: 1-DATABASE-3

  - `status` (string)
    The status of a masking or discovery job.
    Enum: "PENDING", "QUEUED", "RUNNING", "CANCELLED", "FAILED", "SUCCEEDED", "WARNING", "WAITING"

  - `rows_masked` (integer)
    The number of rows masked or profiled so far by this execution. This is not applicable for JSON file type.
    Example: 1000

  - `rows_total` (integer)
    The total number of rows that this execution should mask. This value is set to -1 while the total row count is being calculated. This is not applicable for JSON file type.
    Example: 5000

  - `bytes_processed` (integer)
    The number of bytes masked so far by this execution. This is only applicable for JSON file type.
    Example: 500

  - `bytes_total` (integer)
    The total number of bytes that this execution should mask. This value is set to -1 while the total byte count is being calculated. This is only applicable for JSON file type.
    Example: 5000000

  - `start_time` (string)
    The date and time that this execution was started.
    Example: 2021-05-01T09:51:34.148000+00:00

  - `submit_time` (string)
    The date and time that this execution was submitted.
    Example: 2021-05-01T08:51:34.148000+00:00

  - `end_time` (string)
    The date and time that this execution completed.
    Example: 2021-05-01T11:51:34.148000+00:00

  - `run_duration` (integer)
    The time this execution spent running, in milliseconds.
    Example: 4000

  - `queue_duration` (integer)
    The time this execution spent in the queue, in milliseconds.
    Example: 1000

  - `total_duration` (integer)
    The total time this execution took, in milliseconds.
    Example: 5000

  - `account_id` (integer)
    The account id of the DCT user who started this execution.
    Example: 3

  - `account_name` (string)
    The account name of the DCT user who started this execution.
    Example: username

  - `task_events` (array)
    The progression of steps or events performed by this execution. Only available for executions on masking engines that are version 6.0.14.0 and higher.
    Example: [{"event":"Initializing","status":"SUCCEEDED"},{"event":"Job Completed","status":"FAILED"}]

  - `task_events.event` (string)
    The steps or events a task will perform.
    Example: Job Completed

  - `task_events.status` (string)
    The state of result of the task event.
    Enum: "CANCELLED", "FAILED", "QUEUED", "RUNNING", "SUCCEEDED", "SKIPPED", "NON_CONFORMANT"

  - `hyperscale_task_events` (array)

  - `hyperscale_task_events.name` (string)
    Name of the task (Unload, Masking, Load, Post-Load)
    Example: Unload

  - `hyperscale_task_events.progress` (number)
    progress of the task (between 0 and 1)
    Example: 0.34

  - `hyperscale_task_events.status` (string)
    Enum: "CANCELLED", "CANCEL_INITIATED", "FAILED", "RUNNING", "SUCCEEDED"

  - `hyperscale_task_events.processed_objects` (integer)
    The number of objects (tables) already processed by this task.

  - `hyperscale_task_events.processed_rows` (integer)
    The number of rows already processed by this task.

  - `hyperscale_task_events.processed_constraints` (integer)
    The number of constraints processed by this task (Post-load task only)

  - `hyperscale_task_events.total_constraints` (integer)
    The total number of constraints to be processed by this task (Post-load task only)

  - `hyperscale_task_events.processed_indexes` (integer)
    The number of indexes processed by this task (Post-load task only)

  - `hyperscale_task_events.total_indexes` (integer)
    The total number of indexes to be processed by this task (Post-load task only)

  - `hyperscale_task_events.processed_triggers` (integer)
    The number of triggered processed by this task (Post-load task only)

  - `hyperscale_task_events.total_triggers` (integer)
    The total number of triggers to be processed by this task (Post-load task only)

  - `hyperscale_task_events.start_time` (string)
    The date and time that this task was started.
    Example: 2022-01-02T05:11:24.148000+00:00

  - `hyperscale_task_events.end_time` (string)
    The date and time that this task completed.
    Example: 2022-01-02T05:13:24.148000+00:00

  - `hyperscale_task_events.errors` (array)

  - `hyperscale_task_events.errors.table_name` (string)
    the name of the table for which the error occurred, including the schema.
    Example: public_schema.table_x

  - `hyperscale_task_events.errors.error` (string)
    A textual description of the error.

  - `progress` (number)
    Progress of the task (value between 0 and 1, Hyperscale executions only)
    Example: 0.34

  - `execution_components_total` (integer)
    The total number of execution components in this execution.
    Example: 5

  - `execution_components_processed` (integer)
    The number of execution components processed so far in this execution.
    Example: 3

  - `collection_execution_id` (string)
    The id of the compliance job collection execution this execution is part of, if any
    Example: 54a0cbff-bdc6-49fd-8e71-e8b570524fe9

  - `data_collection_complete` (boolean)
    Indicates whether all peripheral information associated with the execution, including execution components, execution events, logs and discovery results, has been fully collected and finalized.