Flxpoint incident

Integration Disruption - October 13 & 15, 2026

Major Resolved View vendor source →

Flxpoint experienced a major incident on October 15, 2026 affecting Automation, lasting 1h 59m. The incident has been resolved; the full update timeline is below.

Started
Oct 15, 2026, 11:50 AM UTC
Resolved
Oct 15, 2026, 01:49 PM UTC
Duration
1h 59m
Detected by Pingoru
Oct 15, 2026, 11:50 AM UTC

Affected components

Automation

Update timeline

  1. resolved Oct 15, 2026, 08:54 PM UTC

    On October 13 and October 15, several supplier, marketplace and EDI integrations failed to run for part of the day after two updates to our integration platform. Both problems are fixed and all integrations are running normally. EDI documents received during a two-hour window on October 15 (11:50–13:49 UTC) are being reprocessed.

  2. postmortem Oct 15, 2026, 08:57 PM UTC

    # Integration Disruption Post-Mortem - October 13 & 15, 2026 Oct 15, 2026 On October 13 and October 15, several supplier, marketplace and EDI integrations failed to run for part of the day after two updates to our integration platform. Both problems are fixed and all integrations are running normally. EDI documents received during a two-hour window on October 15 \(11:50–13:49 UTC\) are being reprocessed. ## What happened As part of routine maintenance, we updated a shared component that many integrations use to exchange data with suppliers and marketplaces. Two of those updates accidentally removed pieces that some integrations still needed. * **October 13.** The first update affected integrations that connect through older web-service connections, including eBay and several suppliers. Their scheduled jobs failed until a fix went out at 17:33 UTC. * **October 15, from 08:52 UTC.** A follow-up update affected EDI integrations and a further set of supplier and marketplace connections. These jobs failed until a fix went out at 11:44 UTC. * **October 15, from 11:50 UTC.** That fix exposed a second problem. EDI integrations ran and showed as successful, but could not read the documents they received, such as invoices, shipment notices and order acknowledgements. A second fix went out at 13:48 UTC. Every EDI file received during the disruption was kept, so suppliers do not need to resend anything. On both days, integrations that had failed returned to their regular schedule at about 20:00 UTC. ## Timeline \(UTC\) Affected integrations were disrupted from 08:52 to about 20:00 UTC on October 13, and from 08:52 to about 20:15 UTC on October 15. **October 13** * 08:52 — First update released; integrations listed under October 13 below begin failing * 17:33 — Fix released; failures stop * ~20:00 — Affected integrations back on their regular schedule **October 15** * 08:52 — Follow-up update released; integrations listed under "October 15, 08:52–11:59" below begin failing * 11:44 — Fix released; last failure at 11:59, from a job that started before the fix * 11:50 — EDI integrations begin failing to read incoming documents \(jobs still show as successful\) * 13:48 — Second fix released; last unreadable document at 13:49 * 20:02–20:18 — Integrations that failed earlier that day back on their regular schedule * In progress — Reprocessing EDI documents received 11:50–13:49 ## Affected integrations 21 integration types were affected. Find yours below to see which processes were down and when. A dash means it was not affected in that window, and integration types not listed were not affected at all. All times are UTC. **October 13, 08:52–17:33 UTC** * Crow Shooting: Shipments, Send POs/FRs, PO/FR Acknowledgements * eBay: Get Orders, Sync Orders, Sync Listings * Keystone: Shipments, Send POs/FRs, Inventory * Kroll: Shipments, Invoices * PoolCorp: Inventory, Send POs/FRs, Shipments * Promostandards: Inventory * Seawide: Send POs/FRs, Shipments, Inventory **October 15, 08:52–11:59 UTC** * Camuto: Send POs/FRs, Shipments, Invoices * Crow Shooting: Shipments, PO/FR Acknowledgements * Essendant: Inventory * Fanatics EDI: Orders * Flxpoint Standard EDI: Invoices, Shipments, Inventory * Flxpoint Standard EDI V2: Inventory, Shipments, Invoices, Send POs/FRs, PO/FR Acknowledgements * Keystone: Shipments, Send POs/FRs, Inventory * Land N Sea: Inventory, Invoices * McKesson: Shipments, Invoices, PO/FR Acknowledgements, Send POs/FRs * OJG: Shipments, Inventory, Invoices * Orgill: Send POs/FRs * Rothco: Inventory * RSR EDI: Invoices, Shipments, PO/FR Acknowledgements, Send POs/FRs * Seawide: Shipments, Inventory * Sports South EDI: Invoices, Shipments, PO/FR Acknowledgements, Send POs/FRs * TDSynnex: Shipments * Walmart: Sync Listings **October 15, 11:50–13:49 UTC — EDI documents could not be read** * Camuto: PO/FR Acknowledgements, Inventory * Fanatics EDI: Orders * Flxpoint Standard EDI: Inventory * Flxpoint Standard EDI V2: Inventory, Shipments, Invoices, Send POs/FRs, PO/FR Acknowledgements * Land N Sea: Inventory, Invoices * McKesson: Shipments * RSR EDI: Invoices, Shipments, PO/FR Acknowledgements, Send POs/FRs * Sports South EDI: Invoices, Shipments, PO/FR Acknowledgements, Send POs/FRs Integrations that failed in the first two windows did not run again until about 20:00 UTC the same day. In the third window, EDI jobs kept running but could not read the documents they received. ## What this means for your data Most integrations caught up on their own when they resumed. EDI documents from the third window are the one thing still being restored. * **October 13 and the October 15 08:52–11:59 window.** Affected integrations picked up where they left off when they resumed at about 20:00 UTC. Orders, shipments, invoices and purchase orders that were due during the outage were handled on that run, and inventory refreshed with current data. * **EDI documents received October 15, 11:50–13:49 UTC.** Invoices, shipment notices \(with tracking\) and order acknowledgements from this window have not yet appeared in Flxpoint. Your suppliers also have not yet received our receipt confirmations for them. We are reprocessing these documents now; the confirmations will be sent as part of that, and we will update this post when it is complete. EDI inventory files from this window will not be reprocessed, because newer inventory has already been applied. If you still see a missing order, shipment, invoice or acknowledgement from these windows after we confirm reprocessing is complete, contact support with the order or PO number. ## What we're doing to prevent this * Adding automated checks that exercise each type of supplier, marketplace and EDI connection before any update to the shared component is released. * Alerting when an integration cannot read the documents it receives, even if the job otherwise completes. * Changing how EDI documents are retried, so files that fail because of a problem on our side are processed automatically once it is fixed. * Making sure affected integrations return to their regular schedule as soon as a fix is released, not hours later. We're sorry for the disruption to your operations, and thank you for your patience.