ELD Web - April Updates 2026

Improvements

➔    The authentication system has been enhanced to provide a more consistent and predictable account lockout experience when users enter incorrect passwords multiple times. This ensures improved security and reliability across login flows.

➔    We’ve enhanced the ELD Logs experience to provide better visibility into carrier changes within a single driver’s shift. Drivers who switch between multiple carriers during the same day will now have a complete and accurate record of their activity, without overwriting previous carrier information.

➔    We’ve enhanced the Users/Drivers page by introducing a Fleet Sync column for Fleet-integrated accounts. This improvement provides clear visibility into the synchronization status of drivers and users, helping administrators easily identify whether records are synced with Fleet systems.


Deep Dive Improvements

Improved Automatic Account Lockout

The updated implementation standardizes how failed login attempts are counted, how lockouts are enforced, and how accounts are unlocked after the configured duration.

Previously, lockout behavior could be inconsistent in certain scenarios, such as counting failed attempts or handling unlock timing. With this release, these gaps have been addressed to ensure uniform behavior across all authentication attempts.


What’s New

  1. Consistent Failed Attempt Tracking

Failed login attempts are now counted reliably and consistently for each user, preventing mismatches or missed counts.

  1. Accurate Lockout Enforcement

Accounts are locked immediately after reaching the configured maximum number of failed attempts, with no gaps or delays.

  1. Reliable Auto-Unlock Mechanism

Accounts are automatically unlocked after the configured lock duration, allowing users to retry login without manual intervention.

  1. Failure Counter Reset on Success

A successful login clears all previous failed attempts, ensuring lockout calculations restart correctly.

  1. Case-Insensitive Email Handling

Login attempts using different email casing (e.g., uppercase/lowercase) are treated as the same user, ensuring consistent lockout behavior.

  1. Improved Error Handling

The authentication flow has been hardened to avoid server errors (e.g., 500 responses), ensuring stable and predictable responses under all scenarios.


Behavior Summary:

  • Users receive standard authentication failures (e.g., 401) until the failure limit is reached.
  • Once the limit is reached, the account is locked (e.g., 403 or equivalent response).
  • Locked accounts remain inaccessible until the configured lock duration expires.
  • Successful login resets the failed attempt counter.
  • Invalid users continue to receive standard authentication failure responses without errors.

Key Benefits:

  • Improve account security through reliable lockout enforcement
  • Ensure predictable and consistent login behavior
  • Reduce authentication errors and unexpected failures
  • Enhance overall user experience with clear and stable outcomes

Notes:

  • This improvement applies to all users accessing protected APIs or login systems.
  • The feature does not change existing configuration (e.g., max attempts or lock duration); it ensures the system adheres strictly to those settings.
  • No impact to normal login behavior for valid users.

Carrier Information Visibility on Driver Logs

Previously, the Logs screen displayed only the most recent carrier associated with a driver’s activity. In cases where a driver worked for multiple carriers in a single shift, earlier carrier information was overwritten, resulting in incomplete records.

With this enhancement, all carrier transitions are now captured and displayed clearly across the Logs UI and reports.


What’s New

  1. Multi-Carrier Display in Logs

        ·  The Carrier section on the Logs screen now displays all carriers associated with a driver’s shift.

        ·  Each carrier is shown with its respective active time range.

        ·  Information is structured for clarity and easy auditability.

  1. Structured Carrier Timeline Format

Carrier details are displayed in a clear, line-by-line format:

[Carrier A] 

[Start Time] - [Carrier Change Time] 


[Carrier B] 

[Carrier Change Time] - [End Time] 

  1. Support for Multiple Carrier Changes

       ·  Handles multiple carrier switches within a single shift.

       ·  Each segment is recorded with accurate timestamps, ensuring a complete timeline.

Carrier Change Event in Logs:

       ·  A new status event is introduced in the Logs event list whenever a carrier change occurs.

       ·  Displays as a visual indicator (status block) aligned with the exact time of the switch.

Carrier Change Reflected in Reports:

    ·  Certified Log Reports now include carrier change events.

    ·  Events appear alongside other status changes with corresponding remarks.

    ·  Ensures reports provide a complete and compliant record of driver activity.

Key Benefits

  • Track driver activity across multiple carriers in a single shift
  • Maintain accurate and complete ELD records
  • Improve visibility and traceability in shared or reseller environments
  • Reduce ambiguity during audits and inspections

Fleet Sync Visibility on Users/Drivers Page

Previously, there was no direct way to view the Fleet synchronization status of users or drivers from the Users/Drivers table. This made it difficult for administrators to quickly verify sync states or identify discrepancies in Fleet-integrated environments.

With this enhancement, sync status is now surfaced directly in the UI, improving transparency and operational efficiency.


What’s New

  1. Fleet Sync Column (Conditional Visibility)

        ·    A new Fleet Sync column is added to the Users/Drivers table.

        ·    The column is displayed only for accounts with Fleet Sync enabled.

        ·    For accounts without Fleet Sync, the column remains hidden to avoid unnecessary UI clutter.

  1. Sync Status Indicator

       ·    Each user/driver row displays a visual status indicator within the Fleet Sync column.

       ·    The indicator is controlled by the FleetSynced flag:

    • Green button → User/Driver is successfully synced
    • Dark button → User/Driver is not synced

Key Benefits

  • Monitor Fleet sync status directly from the Users/Drivers page
  • Quickly identify and troubleshoot sync issues
  • Improve operational efficiency in Fleet-integrated environments
  • Maintain a streamlined and context-aware user interface


For bug fixes, refer to the PDF Copy: [Customer] ELD Web Release Notes - April 2026

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.