Skip to main content
All CollectionsRelease NotesDrive Microservices Release Notes
Drive Microservices Release Notes, Version 24.9
Drive Microservices Release Notes, Version 24.9

Includes a new ruleset for Canada

Updated over a week ago

This release note describes fixes for EROAD Drive Microservices Version 24.9.

What's New in this Release?

Enhancements:

  • Alberta provincial HOS ruleset (Canada)

  • Limit vehicle, trailer, and dolly selection by terminal

Fixed Issues:

  • Policy endpoint returns soft-deleted policies

  • Job Insights not showing correct driver

  • Vehicle information missing in Route Manager

Environment

Pre-Production

Production

Release Version

v24.9

Proposed Date

Proposed Time

Deployment Duration

Expected Downtime

Enhancements

The following enhancements were completed for this release.

Alberta Provincial HOS Ruleset (Canada) (DFT-266)

We developed a new 70/7 ruleset for the Alberta Province in Canada. In Drive, the ruleset displays as "AB Provincial 70 Hours/7 Days".

This ruleset does not support shift deferrals and driving breaks after 4 or 6 continuous driving periods. Although Alberta does not enforce a cycle, the cycle limits are aligned with Canada Federal rules south of the 60° latitude.

Limit Vehicle, Trailer, and Dolly Selection by Terminal (CAB-271)

We developed an account-level setting so that customers can limit vehicle, trailer, and dolly selection to those in the driver's terminal. After enabling this setting, drivers see only vehicles and equipment assigned to their terminal or unassigned.

Fixed Issues

The following issues were fixed for this release.

Policy Endpoint Returns Soft-Deleted Policies (CAB-1717)

Fixed a policy bug where soft-deleted policies were incorrectly returned. The endpoint now respects the isDeleted flag, ensuring only active policies are retrieved.

Job Insights Not Showing Correct Driver (CAB-1658)

Previously, routes were incorrectly attached to a driver’s vehicle during sign-out and shutdown. This was fixed so that for driver sign-in or vehicle change, a clean-up task ensures that the previous routes are correctly detached, preventing unintended route assignments to other drivers using the same vehicle.

Vehicle Information Missing in Route Manager (CAB-1179)

Previously, Drive would send route assignment changes after routes were completed. We updated the route assignment logic to process re-assignments only after a driver logs in or changes vehicles. Now, routes remain assigned until a driver selects a new vehicle or another driver claims the previous vehicle. This fix improves assignment stability without functionality impact for Route Manager users.

Did this answer your question?