TMS Sync
This article covers the high-level approach to the syncing of TMS data into LoadAi
Overview
The Integrations page shows the connection between LoadAi and your TMS (and, if connected, your ELD provider). Use it to see what data has synced, when, whether anything needs attention, and to manually refresh your data if you don't want to wait for the next scheduled update.
Key Use Cases
- Check when your data last synced successfully.
- See which entities (Loads, Trips, Drivers, Tractors, Trailers, Locations, Customers, Carriers) haven't updated recently.
- Review records that didn't sync cleanly, and look at the original data your TMS sent for any flagged record.
- Manually refresh specific data instead of waiting for the next automatic sync.
Navigation
System > Integrations
The left panel is split into two sections:
- TMS Integration — your connected TMS account, with its last update time shown right under the account name.
- ELD Integration — where you connect an ELD provider (via + ELD Account), separate from your TMS connection.
At the top of the Integrations page, you'll see:
- Last Update Completed on — the date and time of the most recent successful sync.
- Environment — which environment you're viewing (e.g., Production).
- Stale Entities (>30m) — a flag that appears when one or more data types haven't updated in the last 30 minutes.
Stale Entities
If any of your data types haven't refreshed recently, they're called out here by name (for example: Load, Load-Trip, Trip (+1) — with "+1" meaning there are additional stale types not named). Click View details to open the full breakdown, showing every data type LoadAi tracks along with how long it's been since each one last updated:
| Data type | Example |
|---|---|
| Load | 9d 17.2h ago |
| Trip | 2h 28m ago |
| Driver | 5h 9m ago |
| Tractor | 3h 16m ago |
| Trailer | 5h 10m ago |
| Trailer Location | 15d 12.9h ago |
| Customer | 5h 11m ago |
| Carrier | 5h 11m ago |
| Location | 5h 11m ago |
If something in LoadAi looks out of date, this is the first place to check — it tells you whether the underlying TMS data itself is stale, rather than something being wrong in LoadAi.
Refreshing Your Data: Fetch All DataIf you don't want to wait for the next scheduled sync, use Fetch All Data:
- Click Fetch All Data in the top right of the page.
- Choose which data you want refreshed — you can select any combination of Loads & Trips, Drivers, Tractors, Trailers, Customers, Carriers, and Locations.
- Click Fetch Data to start the refresh.
While a refresh is running, the button is temporarily disabled so you don't start a second one on top of it.
Reviewing Sync ErrorsThe Data Sync Error tab lists records that didn't sync cleanly. For each one, you'll see:
- When the error occurred
- Which type of record it affected (Load, Trip, Customer, etc.) and its ID
- A plain-language reason (for example, "Missing Trip," "Missing Load," "Name is required")
- A link to view the raw data your TMS sent for that record, useful if you need to confirm with your TMS admin whether the issue originated there or in LoadAi
You can filter this list by when the error occurred, which data type it affected, the specific error, and whether to include errors you've previously marked as ignored (there's a toggle for that — ignored errors are hidden by default).
A quick note: an empty error list is a good sign, but it doesn't guarantee every record came through exactly as expected. If something looks off in LoadAi and you don't see a matching error here, it's still worth checking the raw data for that record directly.
Events LogThe Events Log tab shows a history of sync activity — who or what triggered each sync and when it was triggered. Completion times aren't always shown for every sync; if you need to confirm a specific sync finished, check the entity's last-updated time under Stale Entities instead.
This article covers general Integrations page behavior. Specific fields, sync frequency, and available integrations can vary by TMS platform — contact your Customer Success Manager for account-specific detail.