Skip to main content

EWA Release 40.2.7

Version 40.2.7 stable: Component Versions​

Version 40.2.7 stable of EWA was released to customers on February 11th 2026.

The compatible versions of the affected runtime components are listed below:

ComponentVersion
Chat Server26.2.51.0
Client Application26.2.25.0
Client Hub26.2.107.0
Data Warehouse Export Service26.2.56.0
EOC Integration26.2.55.0
Export Service26.2.56.0
Insights API26.2.53.0
Form Module API26.2.20.0
HP Link Patient Identity API26.2.53.0
Insights Web26.2.52.0
LiveView API26.2.55.0
Medical Unit Broker26.2.12.0
Migration and Seeding Tool26.2.511.0
Personnel Registration API26.2.1.0
Version Manager API26.2.51.0
Version Manager Client Installer26.2.51.0

Version 40.2.7 stable: New Features​

No new features were included in this release.

Version 40.2.7 stable: Updated Features​

No updated features were included in this release.

Version 40.2.7 stable: Fixes​

Updated At column in the Missions table is set to the current timestamp after running migration​

  • Ticket: 375548735714| DevOps: 37088| Reported by: HSØ
  • Issue: During the upgrade from version 35.9 to 40.2.5, we observed that after a successful migration the client began receiving missions that had already been completed. The UpdatedAt column in the Missions table was set to the current timestamp for those missions.
  • Solution: The solution uses safe backfilling by disabling the trg_mission_updated trigger to prevent mass UpdatedAt changes, processes EMCCId updates in batches of 50,000 to avoid log bloat and locking, and enforces data integrity by removing duplicates (keeping the latest UpdatedAt) before applying a unique constraint on (EMCCMissionId, EMCCId).
  • Affected components: Migration and Seeding Tool and Insights API

Prevent Infinite Log Retry Loop Caused by Invalid JournalId​

  • Ticket: 376813424864 | DevOps: 37131| Reported by: HSØ
  • Issue: ClientApp is sending technical logs to ClientHub that reference JournalId values which do not exist in the server database—typically due to version mismatches or incomplete data synchronization. As a result, the server encounters foreign key constraint violations when attempting to insert these records into the Logs table. This triggers an infinite retry loop, causing the logs to never be successfully stored and the logs table is spammed with error logs increasing the size of the database.
  • Solution: Add server-side validation in log controller to check if JournalId exists before inserting.
  • Affected components: Client Hub

Tested Medical Devices​

All versions of this release have been tested on the listed medical devices and corresponding software versions, ensuring compatibility and performance in the specified environments.

Corpuls​

  • Software versions: 4.3.2
  • SDK version: 4.3.0.0

Zoll​

  • Software version: 02.36.21.00
  • SDK version: 6.44.315