This guide describes how to troubleshoot payload errors and data feed issues
when using Navigation Connect.

## No ENROUTE status received

If you don't receive an `ENROUTE` status, an authentication error likely
occurred. Check for misspelled API parameters or an expired trip token in your
initial `CreateTrip` response.

If the status remains `NEW`, the driver's device might prevent authentication.
Because Navigation Connect does not send error messages for these cases, check the
following scenarios:

- If the navigation app can't find the destination, then confirm you passed a valid destination in the launch URL.
- If no valid route exists, then verify that the origin and destination are correct and reachable by road.
- If the session fails to authenticate, then check for misspelled API parameters or an expired trip token in the `CreateTrip` response.
- If the status remains `NEW` after checking the above scenarios, then have the driver enable precise location and accept the consent prompt in Google Maps or Waze.
- If the driver is in Incognito mode in Google Maps, the app displays an error and the session fails to start. Have the driver turn off Incognito mode.

## Received FAILED or CLIENT_ERROR status at trip start

If the status changes to `FAILED` or `CLIENT_ERROR` when the driver starts a
trip, something blocked trip data sharing. Check for the following causes:

- Driver connectivity issues.
- The driver is using Android Auto or Apple CarPlay.
- The driver didn't accept or revoked consent.
- Challenges with driver authentication.
- The driver started a trip in the United States, but your app doesn't have United States trip data sharing enabled.

## No further trip updates received

If your Google Cloud Pub/Sub topic or `GetTrip` API calls don't receive `FAILED`
or further trip updates after `ENROUTE`, the following issues can cause missing
trip updates:

- Google Maps or Waze quitting unexpectedly.
- Network connectivity issues on the driver's phone.

## Expected payload not received

If you don't receive an expected payload after checking the above steps, and you
confirm all setup is correct, the following can cause missing payloads:

- **Network connectivity issues** may cause payloads to drop.
- **Poor GPS/GNSS signal**: Navigation requires precise location from GPS/GNSS satellites. This may not be possible in underground parking garages, urban canyons, or tunnels. The position of the device in the vehicle can also affect signal quality.
- **Device quality and age**: Older or cheaper devices may have poorer quality GPS chips, affecting location reporting accuracy.

> [!NOTE]
> **Note:** It's unusual for these occurrences to continue over an extended period, especially across multiple trips or drivers. If you continue to see these occurring across multiple drivers or trips, [contact support](https://console.cloud.google.com/google/maps-apis/support). If the occurrence is isolated to one driver or phone, try to debug internally with that driver first.