A bug caused an intermittent “Unknown error updating trips” message to display when editing existing trips.
What’s Fixed
The error message no longer appears.
Trip updates now save correctly and consistently.
On the Dispatch/Schedule screen, some users experienced an issue where events within a run could no longer be moved after attempting to reorder them.
What’s Improved
Event reordering will no longer get stuck.
Dispatchers can continuously move events without interruption.
Updating a passenger’s address and then creating a new trip could cause the client record to revert back to its previous address—without the user saving the change.
What’s Fixed
Client records will no longer update or revert unless a user intentionally saves changes.
Creating a trip no longer modifies or resets passenger address information.
We fixed an issue where odometer values collected by the mobile app were not being returned correctly in the Trip Status and GetRidesByDate endpoints.
What’s Fixed
Odometer values were previously returned as 0 even when collected on mobile.
These endpoints now return the correct odometer readings captured during trips.