Finding GroundXChange Errors
This article walks you through the steps to find and review errors for both Inbound and Outbound GroundXChange (GX) Trips.
Accessing GX Trips
The best way to investigate a GX trip issue — whether you are farming out a trip via GX or receiving one — is to check the Trips > GX Trips area of the Addons tab.
Navigate to Addons → Trips → GroundXChange Trips
The GroundXChange Trips button in the Trips view
Viewing Unresolved Failures
All failed imports — both inbound and outbound — appear under Trips → GroundXChange Trips. A detailed breakdown with an explanation of each failure is available by clicking Unresolved Failures.
The Unresolved Failures banner at the top of the GroundXChange Trips page
Reviewing Error Details
After opening the Unresolved Failures page, all failed trips are listed there. To see the full breakdown of an error, click View Request/Response.
The Unresolved Failures detail page — click View Request/Response for a full error breakdown
Distinguishing Farm-In vs. Farm-Out Errors
The Error Type column shows whether the error relates to a farm-in (inbound) or a farm-out (outbound) trip. Use the following indicators to tell them apart:
- Farm-In (Inbound): The error occurred while your system was receiving a trip from another operator via GX. These entries typically display a plain error label such as
validation_error or
booking_error. - Farm-Out (Outbound): The error occurred while your system was sending a trip to another operator via GX. These entries are prefixed with
outbound_
(e.g., outbound_push_failed) to clearly indicate they relate to an outbound trip.
Farm-Out errors are prefixed with outbound_; Farm-In errors show a plain error type