Customer-facing EDI Resolved Issues

✅ Resolved Issues

Issue: Phone Number Validation Blocking EDI Load Creation

Date Resolved: 10/06/2025
Root Cause: Public API update pushed on Friday, 10/02/25, did not account for all EDI phone number formats.
Reported: 10/06/2025 – 9:06 AM ET
Resolved: 10/06/2025 – 9:51 AM ET
Resolution: Tai Development team was alerted and deployed a fix to support all phone number formats.

Issue: JT AS2 Certificate Change

Date Resolved: 10/14/2025 – 10:00 AM CST
Root Cause: Annual AS2 certificate renewal; prior notification emails were sent to all existing AS2 partners.
Resolution: Partners were instructed to update to the new JT AS2 certificate file provided in earlier communications.

Issue: UF 990 “A” Rejections

Date Resolved: 10/15/2025
Root Cause: Public API naming convention mismatch (“Booked” vs. “Committed”).
Resolution: Updated affected mappings and verified that Acceptance messages are now transmitting correctly

Issue: Public API Outage

Date Resolved: 11/04/2025
Root Cause: Deployment on 11/03/2025 around 10:20 PM ET caused Database exception errors.
Reported: 11/04/2025 – 7:46 AM ET
Resolved: 11/04/2025 – 8:09 AM ET
Resolution: Tai Development team was alerted and deployed a fix

Issue: Public API Outage

Date Resolved: 11/12/2025
Root Cause: We experienced an outage affecting shipment processing through the Public API /Shipping/v2/Shipments endpoint.
Our team rolled back the system updates pushed the night prior to restore full functionality as quickly as possible.
Reported: 11/12/2025 – 9:03 AM ET
Resolved: 11/12/2025 – 9:55 AM ET
Resolution: Tai Development team was alerted and deployed a fix

Issue: Public API Outage

Date Resolved: 12/12/2025 – EOD
Root Cause: On 12/11/2025 around 10:20 PM ET, a deployment was released that defaulted all newly created shipments to use Trailer Type: Van.
Reported: 12/12/2025 – 12:20 PM ET
Resolved: 12/12/2025 – EOD
Resolution: Tai Development team was alerted and deployed a fix

⚡ Recently Resolved / Monitoring

Issue: Public API - Parsing Failures – Shipment Reference Number Validation

Date Resolved: 01/16/2026
Root Cause: A system update deployed on 01/15/2026 introduced new validation logic on the Public API /Shipping/v2/Shipments endpoint requiring values for all Shipment Reference Numbers.
Historically, EDI 204 integrations have allowed the Temperature, Quote Due By Date, and Trailer Number reference fields to be sent with blank values (“”) when those details were not provided in the EDI file. The new validation rejected empty strings, causing widespread EDI parsing failures.
Reported: 1/16/2026 – 8:45 AM ET
Resolved: 1/16/2026 – 10:32 AM ET
Resolution: Tai Development team rolled back the validation change to restore previous functionality and confirmed that empty reference values are once again accepted. All affected integrations returned to normal processing following the rollback.