---
title: "POST /executions/retry"
method: POST
path: "/executions/retry"
---

# POST /executions/retry

`POST /executions/retry`

Queue file executions to be retried.

## Request body

- RetryExecutionsRequestContent
  - `condition` RetryExecutionSelectionCondition, required — Specify the file executions to retry. Stedi will retry all executions matching the given criteria. For example, you can retry all file executions with a `FAILED` status within a specific date range. Note that Stedi only retries each `executionId` once. Each retry attempt is stored as a new file execution within Stedi. If you need to retry a file multiple times, you'll need to pass the ID of the latest retry attempt to this endpoint.
    - `executionIds` string[] — A list of file execution IDs. These are unique identifiers 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.
    - `direction` 'INBOUND' | 'OUTBOUND' | 'UNKNOWN' — 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.
    - `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.
    - `partnershipId` string — Specify executions associated with a specific partnership. This is the `partnershipId` property in the file execution record. You can also find this ID on the [Trading partners](https://www.stedi.com/app/core/partnerships) page under **Partnership identifier**.
    - `status` 'COMPLETED' | 'PARTIALLY_COMPLETED' | 'FAILED' | 'IGNORED' | 'IN_PROGRESS' | 'RETRYING' | 'RETRIED' | 'STARTED' — 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.
    - `from` string, date-time — Specify executions processed after this timestamp, in ISO 8601 format. For example, `2023-08-28T00:00:00Z`.
    - `to` string, date-time — Specify executions processed before this timestamp, in ISO 8601 format. For example, `2023-08-28T00:00:00Z`.

## Response `200`

RetryExecutions 200 response

## 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)