This release note describes enhancements and fixes for EROAD 360 Version 26.5. Unless otherwise indicated, changes apply to all users.
What's New in This Release?
What's New in This Release?
New Route Manager features:
Automatic arrival trend card
Manually recorded stops card
Additional features
Fixed issues:
Unexpected application error in 360
360 shows geofence exit when vehicle did not exit geofence
Driver Edits Report shows incorrect events
Environment | Pre-Production | Production |
Proposed Date | March 24, 2026 | April 12, 2026 |
Proposed Time | 7:00 PM CST | 8:00 PM CST |
Deployment Duration | 3.5 hours | 3.5 hours |
Expected Downtime | Less than 30 minutes | Less than 30 minutes |
New Features: Route Manager
This release includes two arrival accuracy cards that are visible at the top of the Route Manager home page. The cards provide an at-a-glance way to monitor automated arrivals and manually recorded stops.
For details, refer to the Route Manager Home Page help article.
Automatic Arrival Trend Card
The Automatic Arrival Trend card shows how reliably the system is auto-detecting arrivals at stops over time. This information helps you monitor automatic arrival performance and easily compare performance against the previous 7 days, prompting further investigation if there is a noticeable difference.
Typical use cases include:
Validating that automatic arrival is working consistently across different days, sites, or fleets.
Detecting data quality issues.
Manually Recorded Stops Card
The Manually Recorded Stops card highlights stops that were recorded manually, missed, or skipped. This provides visibility into where automation is not being used or not working as expected. Clicking a metric link enables you to drill down to the specific stops or routes where manual recording occurred.
Note: This card applies retrospectively. After go-live, the system starts collecting and surfacing manual stop data, so historical trends and patterns become available over time.
Typical use cases include:
Identifying drivers or routes with high levels of manual recording.
Distinguishing between legitimate manual overrides (e.g., edge cases in which automation does not work) and avoidable manual activity.
Tracking improvement over time as configuration and training reduce dependency on manual recording.
Additional Features
Also new on the Route Manager home page:
The Ready to start and Incomplete metrics on the Route readiness card are now links. When you click a link, 360 filters the routes list to show the applicable routes that are either ready or not ready.
A new Stop status dropdown menu enables you to filter the routes list for any of the following stop statuses: Manually arrived, Missed, Skipped, and Automatically recorded.
Fixed Issues
The following issues were fixed for this release.
Unexpected Application Error in 360 (BO360-1187)
We resolved an issue that caused occasional “Unexpected Application Error” messages when users logged into 360 or returned to the Phoenix tracking maps after switching browser tabs. Map navigation and login should now work reliably without unexpected errors.
360 Shows Geofence Exit When Vehicle Did Not Exit Geofence (BO360-1248)
360 reported geofence exit events when vehicles were not moving. To fix this issue, we improved the accuracy of location matching around areas with densely stacked locations to prevent mismatched/spurious entries and exits.
Driver Edits Report Shows Incorrect Events (BO360-1320)
The Driver Edits Report listed events, such as Login and Vehicle Change events, that do not meet the criteria for this report. This issue was fixed so that the report correctly reports driver edits (add status, edit status).