Dynamic scheduling recalculating estimated travel time and setting travel start before working hours

[AnaVragovic]

Hi everyone,

we are using dynamic scheduling and we have noticed that when it was triggered it calculated estimated travel duration as 58 minutes, set scheduled travel start to 08:00:00 (when working hours start) and scheduled start  to 08:58:27, then changed estimated travel duration to 59 minutes and updated scheduled travel start to 07:58:45.

We have configured dynamic scheduling to use straight line estimate, not Google Map API

Does anyone have any idea why it even recalculates the estimated travel time, and the second, why would it set travel start before agent's start of working hours if there is no setting allowing this? We have not configured any work parameters.

Thank you

[Tanushree Maiti]

Hi @AnaVragovic 

Refer: Dynamic scheduling system properties 

Configuring Dynamic Scheduling 

ravel calculation method	work.management.travel.calculation. dynamic_scheduling	Uses Google Maps API, Beans.AI, or straight line estimates to calculate estimated agent travel time and distance to task locations when agents are assigned tasks using dynamic scheduling.
Distance calculation method	work.management.distance.calculation.dynamic_scheduling	Calculates agent’s estimated travel time and distance to the task location based on either Google Maps API, Beans.AI, or straight-line. If the Use Google Maps API for travel time estimates geolocation property is enabled, then you can select Google Maps API or straight-line estimates in the properties for calculating estimated travel time and distance. If the Use Google Maps API for travel time estimates is not enabled, then the system uses the value in the Estimated Travel Duration field in the work order task to determine task assignment for the agent. Type: choice list Default value: Use straight line estimate.

Refer: 

https://www.servicenow.com/community/field-service-management-forum/dyanmic-scheduling-and-travel-du...