Understanding How Salesforce Field Service Calculates Travel Time on the Gantt

For Salesforce Field Service (FSL, Field Service Lightning) to calculate travel time, both the origin and destination of each travel leg must be geocoded. Below are the most common reasons travel does not appear on the Gantt and the steps to resolve them.

Why Travel Time Is Missing for the First and Last Legs

If travel is not calculated for the first leg (from the resource's home base to the first appointment) or the last leg (from the last appointment back to home base), it means the resource's home base address is not geocoded.
The resource home base address is defined on the Service Territory Member record. Verify that a well-formatted, complete address is entered on the Service Territory Member record so it can be geocoded by Salesforce. If the resource's home base is the office location, use the address from their Service Territory record instead.

Why Travel Time Is Missing Between Appointments

If travel between two Service Appointments is not displayed on the Gantt, it means that one or both of the Service Appointment addresses have not been geocoded. Check the address on those Service Appointment records and ensure they are complete and well-formatted.

How to Check Geocoding Status

Add the Data Integration related list (formerly called Clean Rules) to the relevant record's page layout to see the current geocoding state. This shows whether Salesforce has successfully geocoded the address.

Impact of the Bypass Trigger Checkbox on Travel Calculation

The Salesforce Field Service Managed Package includes a trigger that recalculates travel times when a Service Appointment's latitude or longitude changes. However, if the latitude or longitude is updated by Salesforce's platform geocoding or Data Integration rules, and the Bypass Trigger checkbox is set to true on the Service Appointment, the Managed Package travel calculation trigger does not fire and travel time is not recalculated.