DAT Solutions Internal
Conflict with posting reference ids after switch from FTP to REST
Updates
-
Jan 15, 2026 9:51 AM PST
ATS (customer) is unable to repost some loads via REST because they are trying to reuse reference ids from previously FTP'd loads. The incident was resolved after confirming that the customer, ATS, was able to successfully repost loads by deleting their outdated postings, either on their own or with assistance from Customer Support. There have been no further errors or reports from the customer since the mitigation steps were implemented.
Resolved – customer impact mitigated; systemic behavior tracked in HELP‑73576 / VA follow‑ups; guidance documented for future FTP→REST migrations.
Resolved -
Dec 10, 2025 10:03 AM PST (1 month, 4 days, 23 hours, and 48 minutes earlier)
ATS (customer) is unable to repost some loads via REST because they are trying to reuse reference ids from previously FTP'd loads. The incident was mitigated by confirming that the customer, ATS, resolved the issue on their side, which allowed them to repost loads successfully. Additionally, the communication established possible avenues for the customer to delete postings themselves or have Customer Support assist with the deletions.
Monitoring -
Dec 9, 2025 11:28 AM PST (22 hours and 34 minutes earlier)
ATS (customer) is unable to repost some loads via REST because they are trying to reuse reference ids from previously FTP'd loads.
Investigating