EDI Processing Delays

We've now resolved the incident. Thanks for your patience.

Our underlying service provider is currently stable, and no file duplication is occurring. There may be some moderate delays (minutes) in some processes. We will hold this incident as open until everything is fully back to normal, but no action is needed at this point.

We have identified a second scenario that could cause duplicate EDI sends due to a latency / retry issue related to the underlying performance issues. We have just released a mitigation and will include any items related to this issue in our incident follow up.

At the present time, data is flowing with some delays. We will continue to monitor the status with our service provider and will provide updates here only when the status changes.

If you would like active notifications when things change, please subscribe to updates on this site.

Please note while we're still awaiting resolution from our underlying service provider, we have mitigated the duplication issue. We will provide our next update at 6pm EST. Thanks for your patience.

Inbound and outbound EDI processing is still delayed, sometimes upwards of 30 minutes, as we continue to await resolution from our underlying service provider. Please note this is impacting 0.03% of our traffic on the network. If you are directly impacted you will be contacted by your client success manager.

Inbound and outbound EDI processing is still delayed, sometimes upwards of 30 minutes, as we continue to await resolution from our underlying service provider.

As a follow up to use case 2 from previous updates we've deployed changes to prevent sending duplicate EDI messages.

Status has not changed since the last update:

1. Inbound and outbound EDI processing is delayed, sometimes upwards of 30 minutes
2. In certain cases, we may be sending duplicate EDIs. You can identify this as flows which have run for longer than 15 minutes. In the case that this has happened, we will be able to provide a full log of duplicate messages when this incident has resolved.

We are currently addressing #2 above and expect to have a fix in within the next 2 hours.

We have narrowed the EDI problem down to the following use cases:

1. Inbound and outbound EDI processing is delayed, sometimes upwards of 30 minutes
2. In certain cases, we may be sending duplicate EDIs. You can identify this as flows which have run for longer than 15 minutes. In the case that this has happened, we will be able to provide a full log of duplicate messages when this incident has resolved.

We are currently addressing #2 above and expect to have a fix in within the next 2 hours.

We are currently experiencing latency issues with ANSI X.12 EDI processing due to a performance issue with an underlying service provider. Any failed messages in Flow will be reprocessed by our team once the underlying issues are resolved.

We will communicate with any impacted customers directly regarding any downstream processing issues.