4-30-26 Release Notes

Web Updates:

Web Dispatch:

Forcing or Shopping Trips onto Runs Now Works Correctly

An issue in Web Dispatch was causing an “Error Forcing Trip” message when attempting to shop or force a trip onto a run, preventing the trip from being assigned. This affected a limited number of clients. The issue has now been resolved — trips can once again be successfully assigned to runs from Web Dispatch.

API Updates:

ModivCare API:

Trips No Longer Incorrectly Canceled After Completion

Previously, a trip that was completed and marked as a no show in Mobile could still be incorrectly canceled by the Modivcare API for up to 2 hours afterward. This issue has been resolved — performed trips can no longer be canceled through the Modivcare API.

Webhooks Now Fire When a Driver Logs Into a Route

Previously, when a trip was assigned to a route without a driver, the initial webhook was sent without driver details, and no updated webhook was sent after a driver later logged into that route. This has now been corrected for the Modivcare integration — webhooks will properly fire with driver information whenever a driver is assigned or logs in.

External API:

Address Validation Errors on API Resolved

Previously, valid trip addresses were sometimes rejected with 400 “invalid address” errors when submitted through the API, even though the address data was correct. This issue has been fixed — properly formatted addresses are now accepted without error.