When Stedi encounters EDI processing failures, it displays them on the Files page and emits a file.failed.v2 event.

​
Inbound EDI

When Stedi 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 guide or the base X12 specification. 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.

​
Outbound EDI

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

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

Stedi 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.v2 event. Stedi displays each delivery attempt and the failure details on the Files page.

​
Ignore failed files

Ignoring a failed file changes its status to Ignored and removes it from your list of failed files. You can bulk retry ignored files at any time or use filters to remove them from your dashboard view.

To ignore failed files individually:

  1. Go to the Files page and click the name of the file you want to ignore.
  2. Click Ignore.

To bulk ignore multiple failed files:

  1. Go to the Files page.
  2. Filter the list to the failed files you want to ignore.
  3. Click Bulk actions and select Bulk ignore.

​
Retry files

To retry failed files individually:

  1. Go to the Files page and click the name of the file you want to retry.
  2. Click Retry.

To bulk retry all failed files:

  1. Go to the Files page.
  2. Filter the list to show only failed files.
  3. Click Bulk actions and select Bulk retry.

​
Retry events

You can retrigger events for successfully processed files. This feature makes it easier to test your end-to-end integration – for example, triggering webhooks – without continually reprocessing the same files.

To retry an event:

  1. Go to the Files page and click the name of the processed file.
  2. Go to the Events tab.
  3. Click the ellipses (…) next to an event and select Retry.

​
Diagnosing failures

Stedi displays all of the events associated with each file execution and transaction in the dashboard. You can use this information to quickly debug issues and understand how your data flows through Stedi. Visit Monitor transactions for details.