Issue with Google API with field service management (FSM) dynamic schedulingIssue When Dynamic Scheduling runs, it is often returning null values when getting travel times and then excludes assigning to certain work blocks. This specifically occurs if the Work Order Task is not the first task of the day for a given agent/technician and the location is different on the second task. Steps to reproduce: Schedule a Work Order Task such that you know it will go to a specific agentCreate a second task for the same agent but use a different location than the first task.Note that it assigns for the next day instead of today even though the agent has plenty of availabilityReleaseParisResolutionThis particular issue can be resolved by changing the property on field service management (FSM) for travel time for Dynamic Scheduling to use the straight-line method rather than the Google API.