Failures and retries in Stedi Core
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.
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.
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.
Managing failures with events
file.failedevent 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.
Have an idea for something we could improve? Page not clear? We love feedback - send us a message.