---
title: "GET /executions/{executionId}"
method: GET
path: "/executions/{executionId}"
---

# GET /executions/{executionId}

`GET /executions/{executionId}`

Retrieve the file execution details for a given `executionId`.

## Path parameters

- `executionId` string, required — A unique identifier for the file execution within Stedi. This ID is included in the file processed event, or you can retrieve it manually from the file's details page within the Stedi portal.

## Response `200`

GetExecution 200 response

- GetExecutionResponseContent
  - `createdAt` string, date-time, required — The date and time when the resource was created, in ISO 8601 format. For example, `2023-08-28T00:00:00Z`.
  - `updatedAt` string, date-time, required — The date and time when the resource was last updated, in ISO 8601 format. For example, `2023-08-28T00:00:00Z`.
  - `executionId` string, required — A unique identifier for the processed file within Stedi. This ID is included in the transaction processed event. You can also retrieve it manually from the file's details page in the Stedi portal.
  - `status` 'COMPLETED' | 'PARTIALLY_COMPLETED' | 'FAILED' | 'IGNORED' | 'IN_PROGRESS' | 'RETRYING' | 'RETRIED' | 'STARTED', required — The status of the execution. - You can only retry executions with a `FAILED` or `IGNORED` status. - An execution is `COMPLETED` when Stedi has finished processing the file with no errors. If the file is an outbound file, a `COMPLETED` status also means that Stedi successfully delivered it to the configured connection.
  - `direction` 'INBOUND' | 'OUTBOUND' | 'UNKNOWN', required — The direction of the transaction. Inbound transactions are those you receive from a payer, provider, or other trading partner. Outbound transactions are those you send to a payer, provider, or other trading partner.
  - `transactionCount` number — The number of individual transactions included in the file.
  - `faultCount` number — The number of errors that occurred during processing. If the file was successfully processed completely, this value is `0`.
  - `faultCode` 'DELIVERY_FAILURE' | 'FAILED_TO_EXTRACT_BUSINESS_IDENTIFIERS' | 'FAILED_TO_FIND_GUIDE' | 'FAILED_TO_FIND_LOCAL_PROFILE' | 'FAILED_TO_FIND_PARTNER_PROFILE' | 'FAILED_TO_FIND_PARTNERSHIP' | 'FAILED_TO_FIND_PROFILES' | 'FAILED_TO_FIND_RECEIVER_PROFILE' | 'FAILED_TO_FIND_SENDER_PROFILE' | 'FAILED_TO_FIND_CONNECTION' | 'FAILED_TO_GENERATE_CONTROL_NUMBERS' | 'FAILED_TO_PARSE' | 'FAILED_TO_PARSE_METADATA' | 'FAILED_TO_TRANSLATE' | 'FAILED_TO_ACK' | 'FAILED_TO_ACK_INTERCHANGE' | 'FILE_NOT_FOUND' | 'INVALID_EVENT' | 'INVALID_CONFIGURATION' | 'MISMATCHED_PARTNERSHIP_CONNECTION' | 'MISSING_FUNCTIONAL_GROUP_CONTROL_NUMBER' | 'MISSING_FUNCTIONAL_GROUP_RELEASE' | 'MISSING_INTERCHANGE_CONTROL_NUMBER' | 'MISSING_TRANSACTION_SET_CONTROL_NUMBER' | 'MISSING_RECEIVER_ID' | 'MISSING_RECEIVER_QUALIFIER' | 'MISSING_SENDER_ID' | 'MISSING_SENDER_QUALIFIER' | 'MULTIPLE_MATCHING_GUIDES' | 'MULTIPLE_MATCHING_TRANSACTION_SETTINGS' | 'MULTIPLE_PARTNERSHIPS' | 'NO_TRANSLATION_OUTPUT' | 'NO_TRANSACTION_SETS' | 'NOT_SUPPORTED' | 'NO_FUNCTIONAL_GROUPS' | 'NO_USAGE_INDICATOR_CODE' | 'PREVIOUSLY_RETRIED' | 'TRANSLATION_ERROR' | 'UNKNOWN_ERROR' — A code specifying the reason for the fault. This code appears in the `code` property of the HTTP error response.
  - `faultMessage` string — A message providing more information about the fault. Note that if there are multiple faults, Stedi sets the first fault as the code and corresponding message.
  - `fileType` 'CSV' | 'EDI/EDIFACT' | 'FILEPART' | 'JSON' | 'PSV' | 'JSON/STEDI-GUIDE' | 'TSV' | 'UNKNOWN' | 'EDI/X12' | 'XML' | 'ZIP' — The file format. For example, `EDI/EDIFACT` for an EDIFACT file or `EDI/X12` for an X12 EDI file.
  - `retryable` boolean — If `true`, you can retry the file in the Stedi portal.
  - `parentExecutionId` string — The ID of this execution's parent execution, if it is part of a retry chain. When you retry a file, Stedi creates a child execution with a new ID and links it to the original (parent) execution.
  - `childExecutionId` string — The ID of this execution's child execution, if it is part of a retry chain. When you retry a file, Stedi creates a child execution with a new ID and links it to the original (parent) execution.
  - `partnershipId` string — The unique identifier for the partnership within the Stedi platform. A partnership describes all aspects of the EDI relationship between two profiles in your Stedi account, such as which transaction sets they will exchange and other important information for processing EDI files.
  - `connectionType` 'BUCKET' | 'AS2' | 'STEDI_FTP' | 'REMOTE_FTP' | 'STEDI_ACCOUNT_FTP' — The type of connection used for file delivery.
  - `connectionId` string — An autogenerated identifier for the connection within the Stedi platform.
  - `source` ExecutionSource — The source of the file, including the directory where Stedi received it and the file name.
    - `dirname` string, required — The directory where Stedi received the file for processing.
    - `name` string, required — The name of the file.
  - `mode` 'test' | 'production' | 'other' | 'unknown', required — Indicates whether the file execution contains test or production data. Stedi determines this from the value in [`ISA15` (Usage Indicator Code)](https://www.stedi.com/edi/x12/segment/ISA#ISA-15).
  - `artifacts` Artifact[] — A list of artifacts related to the transaction. Input artifacts represent the original transaction data Stedi received before processing. Output artifacts represent the processed data. For example, for an inbound 835 ERA from a payer, the input artifact would be the original X12 EDI, and the output artifact would be the JSON representation of the ERA.
    - `artifactType` 'text/csv' | 'application/edifact' | 'application/filepart' | 'application/json' | 'application/pdf' | 'text/psv' | 'text/tsv' | 'application/edi-x12' | 'application/xml' | 'application/zip' | 'image/jpeg' | 'image/png' | 'image/tiff' | 'text/plain' | 'unknown', required — The format of the artifact.
    - `usage` 'attachment' | 'input' | 'metadata' | 'output', required — The type of data the artifact contains. For example, an input artifact represents the original data Stedi received before processing, while an output artifact represents the processed data. For example, for an inbound 835 ERA from a payer, the input artifact would be the original X12 EDI, and the output artifact would be the JSON representation of the ERA.
    - `sizeBytes` number, required — The size of the artifact in bytes.
    - `url` string, required — A URL to download the artifact.
    - `model` 'execution' | 'fragment' | 'transaction' | 'fault', required — The model of the artifact, which indicates the type of process or operation it represents. For example, an execution artifact represents a file that was processed, a fragment artifact represents a part of a larger transaction, and a fault artifact represents an error that occurred during processing.
  - `deliveryReports` DeliveryReport[] — Details about delivery attempts for outbound files./n/nStedi attempts to deliver a file to all configured connections every 6 minutes for up to 3 total attempts. If it cannot deliver the file after the third attempt, it marks the file execution as `FAILED` and emits the file failed event.
    - `createdAt` string, date-time, required — The date and time when the resource was created, in ISO 8601 format. For example, `2023-08-28T00:00:00Z`.
    - `id` string, required — A unique identifier for the delivery attempt.
    - `executionId` string, required — A unique identifier for the processed file within Stedi. This ID is included in the transaction processed event. You can also retrieve it manually from the file's details page in the Stedi portal.
    - `partnershipId` string, required — An identifier for the partnership within the Stedi platform.
    - `connectionType` 'BUCKET' | 'AS2' | 'STEDI_FTP' | 'REMOTE_FTP' | 'STEDI_ACCOUNT_FTP', required — The type of connection used for file delivery.
    - `connectionId` string, required — An autogenerated identifier for the connection within the Stedi platform.
    - `attempt` number, required — The attempt number for the delivery.
    - `filename` string, required — The name of the file Stedi attempted to deliver.
    - `status` 'FAILED' | 'DELIVERED', required
    - `message` string, required — A message providing more information about the delivery attempt. For example `Delivered to sftp://transfer.us.stedi.com/outbound/06bdccdc-4ab9-4add-b1dc-a76a0183f299.x12'.
    - `metadata` DeliveryReportMetadata — Metadata about the file delivery.
      - `attempts` number — The total number of delivery attempts for the file.
      - `mdn_file` MdnFile — The location of the Message Disposition Notification (MDN). This is only relevant for AS2 connections.
        - `repository` string, required — The repository location of the MDN file.
        - `pointer` string, required — The pointer to the specific MDN file.

## Other responses

- `400` — BadRequestException 400 response
- `401` — UnauthorizedException 401 response
- `403` — AccessDeniedException 403 response
- `404` — ResourceNotFoundException 404 response
- `409` — ResourceUnderChangeException 409 response
- `422` — UnprocessableEntityException 422 response
- `429` — ThrottlingException 429 response
- `500` — ServiceException 500 response
- `503` — ServiceUnavailableException 503 response
- `504` — GatewayTimeoutException 504 response

---

[API](https://skmtc.net/stedi/apis/core.md) · [All operations](https://skmtc.net/stedi/apis/core/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/stedi/core/revisions/172bd33e0d66/schema)