Skip to main content

Chain Release Notes — February 2026

Written by Madhav M
Updated yesterday

_Release window: February 1, 2026 to February 28, 2026_

New features

  • Added geofence options for shipment stops, including map-based radius and polygon boundaries. Teams can define custom stop areas directly on the map instead of using one default shape. Radius mode is quick for simple locations, while polygon mode supports irregular layouts.

  • Expanded tracking-provider support with additional ELD integrations. This expands coverage for fleets that use different telematics systems. Teams can connect supported providers without custom one-off handling.

  • Added connection tags and custom tags in connection and workspace settings. Teams can label integrations by business context and filter them faster. This makes day-to-day management cleaner when multiple systems are connected.

  • Added team-member role support in CRM. Teams can control CRM access more clearly by role. This helps keep account actions and visibility aligned with responsibilities.

  • Added child-workspace coverage in workspace and posting actions. Child workspaces are now included more consistently in posting-related steps. Teams working across parent and child structures should see fewer context mismatches.

  • Added Infios app enablement support. Teams can activate Infios-related functionality through standard setup steps. This reduces setup friction when onboarding the integration.

  • Added file upload support in chat, along with message state improvements. Users can share supporting files directly in active conversations. Message updates also stay more consistent while chats are busy.

Improvements

  • Updated driver onboarding and shipped driver app flow improvements. The onboarding path is more consistent from setup to completion. Teams should see fewer interruptions while preparing drivers for live usage.

  • Improved chat usability with editor updates and better chat-list handling. Message drafting and list behavior now feel smoother in active channels. This helps teams move between conversations with fewer interruptions.

  • Expanded stop activity visibility so stop events show fuller history. Users can review more of the event timeline in one place. This makes it easier to confirm what happened at each stop.

  • Improved offer and booking handling, including reply and condition updates. Offer responses and condition logic now behave more predictably. Teams should have a smoother path from negotiation to confirmation.

  • Expanded checkpoint timezone handling to include Mountain Time. Time-based checks now support a broader set of operating regions. This helps teams avoid timing confusion across time zones.

Bug fixes

  • Fixed real-time chat sync issues in offer-related conversations. Message and channel updates now appear more reliably during active offer activity. Teams should see fewer cases where chat state lags behind recent actions.

  • Fixed issues with required fields and condition handling in key workflows. Data-entry behavior is now more consistent during shipment updates. Teams should see fewer blocked saves from inconsistent validation states.

  • Fixed workspace context issues that could affect account switching. Workspace selection now stays more stable while navigating between accounts. This reduces incorrect context carryover in multi-workspace usage.

  • Fixed shipment filtering and shipment-row interaction edge cases. Shipment list actions now respond more consistently when filters are applied. Users should see fewer broken interactions in filtered views.

  • Fixed assignment-related issues that could affect driver and dispatcher workflows. Assignment behavior now applies more reliably in these scenarios. This reduces mismatches during operational handoffs.

  • Fixed cases where shipment pages could fail when partial data was returned. Shipment pages now handle partial errors more gracefully. Users can still access key shipment information instead of seeing a full view failure.

Behind the scenes

  • Internal reliability and quality improvements were applied across core workflows. These updates focus on consistency and long-term platform stability. No extra setup is required from customer teams.

Did this answer your question?