EWA Release 40.2.13
Version 40.2.13 stable: Component Versions
Version 40.2.13 stable of EWA was released to customers on June 25th 2026.
The compatible versions of the affected runtime components are listed below:
| Component | Version |
|---|---|
| Client Application | 26.6.30.0 |
Version 40.2.13 stable: New Features
No new features were included in this release.
Version 40.2.13 stable: Updated Features
No updated features were included in this release.
Version 40.2.13 stable: Fixes
Data not sent to server / Journal delete issue on unstable connection
- Ticket: 419494920408, 419301778627, 415975383250, 410594548970, 418578145493, 421151749330
- DevOps: 39731
- Reported by: HSØ, Helse Vest, Helse Midt-Norge, Helse Nord
- HubSpot Title: Journaler sendes ikke til server, Status update rejected - log spamming, Utvidet offline - Får ikke fullført journaler, Slettede Journaler, Journal må fullføres i innsynsklient, P12437 Journaler blir stående som ikke fullført og uten data selv om signert
- Internal Reference: HINC0059477(Helse Midt-Norge), P12437(Helse Vest)
-
Issue: On low or unstable connections, deleting a journal could trigger an invalid all‑null update rejected by the server (409), blocking the strict FIFO send queue and stopping all subsequent journal syncing. This could also wipe journal data and cause Overview tiles to show "{Not Found}".
-
Solution:
- Improved delete handling: when a journal is already deleted or its in‑memory model is missing, the app now sends a status‑only update instead of rebuilding a full update, preventing invalid requests and data loss.
- Unblocked send queue: failed journal updates are now skipped so they do not block the entire FIFO queue.
- Fixed tile labels: deleted/aborted journals now correctly display localized "Deleted" / "Aborted" text instead of "{Not Found}".
-
Affected components: Client Application
✅ Affected components
For release 40.2.12 release we recommend only client application
- Client Application
✅ Testing Focus Areas for 40.2.13 Fix
🧾 Journal Delete & Sync Resilience
Validate deleting a journal on a stable connection works as expected and preserves all data on the server Verify re‑deleting a journal (especially after a slow/unstable connection) does not cause data loss or trigger sync errors Ensure no "Data not sent to server" error appears during repeated delete attempts
🔄 Send Queue Behavior
Simulate low/unstable network conditions and verify that one failed journal update does not block other journals from syncing Confirm that subsequent journal updates are successfully sent even if one fails (no FIFO queue blockage)
📋 Overview Tile Labels
Verify that deleted and aborted journal tiles display the correct localized labels ("Deleted" / "Aborted") Ensure "{Not Found}" is no longer shown under any delete scenario Validate localization across supported languages (NO/EN/SV/DA/DE)
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.4.4
- SDK version: 4.4.0.0
Zoll
- Software version: 02.36.21.00
- SDK version: 6.44.315