Home /  Core / 

Failures and retries in Stedi Core

When Core encounters EDI processing failures, it displays them in the File Executions tab and emits a file.failed event.

Ingesting EDI

When Core ingests EDI, it must first match the data to a partnership and then validate the incoming EDI according to the partnership configuration. Failures may occur when the file does not contain sufficient heading data to match transactions to an existing partnership or when the incoming file contains invalid EDI.

Core only marks an incoming file as successfully processed when all the individual transaction sets within the file are valid against either the base X12 specification or the guide (if specified). If one transaction set is invalid, Stedi flags the entire file as failed.

Other processing failures may occur occasionally, most commonly for missing configuration or misconfigured data. Failure causes include:

  • Stedi cannot find a profile record matching the ISA headers.
  • Stedi cannot find a partnership record defined for the two profiles detected.
  • Stedi received a corrupt or unparseable file.

Generating EDI

Core uses the Stedi guide and other partnership settings to generate valid EDI with the proper envelope and control numbers. Failures may occur when Core tries to deliver the file to a configured connection.

After generating EDI, Core marks the file as successfully processed after delivery to all configured connections. Core does not display transactions from within files that have failed delivery.

Core attempts to deliver a file to all configured connections up to three times before marking the file execution as FAILED. Core displays each delivery attempt, including failure details, in the UI and emits the [file.failed](/docs/core/events#filefailed) event after the third attempt.

Manual retries

You can manually retry failed files on the File executions page in Core’s UI. To retry files, click Retry. Core automatically retries all files with the FAILED status.

Managing failures with events

Stedi generates a file.failed event and displays the error context in the UI. After you address the cause of the failure, you can automate retries by consuming these events and re-uploading the source file to Core.
Ingesting EDIGenerating EDIManual retriesManaging failures with events


Have an idea for something we could improve? Page not clear? We love feedback - send us a message.


Build EDI integrations fast, without being an EDI expert

Start building
  1. Twitter
  2. GitHub
Backed by
AdditionBloomberg BetaFirst RoundStripeUSV
Customer AgreementService TermsPrivacy Notice

Stedi is a registered trademark of Stedi, Inc. All names, logos, and brands of third parties listed on our site are trademarks of their respective owners (including “X12”, which is a trademark of X12 Incorporated). Stedi, Inc. and its products and services are not endorsed by, sponsored by, or affiliated with these third parties. Our use of these names, logos, and brands is for identification purposes only, and does not imply any such endorsement, sponsorship, or affiliation.