Release notes

Releases summary

What's new

• We have added support for the Execution Delay parameter in FIX Server session profiles. This allows configuring a random execution delay (in milliseconds) applied to incoming trade requests, on a per-symbol or session-wide basis. The parameter is available via Cloud and supports profile import/export.
• We have added support for a new per-symbol parameter Throttle Bypass on MT4 Bridge and MT5 Gateway. When configured, a market-data update is sent immediately if the top-of-book bid or ask moves by at least the specified number of points, bypassing the normal throttling interval. Setting the value to 0 means any price change bypasses throttling. If not set, existing throttling behavior is unchanged.

---

What's new

• We have added an opt-in performance diagnostics parameter to the MT5 DataWarehouse plugin that logs per-hook latency on demand, helping diagnose throughput issues without impacting normal operation when disabled.

---

Bug fixes

• We have fixed an issue where changing a FIX session symbol's market data pool via the Configuration would silently stop market data flowing to the connected client.

---

What's new

• Force-Delete for Working Orders. Managers can now force-delete a working order independently of the standard cancel flow. The Working Orders grid now offers two distinct actions: Cancel (for standard order cancellation) and Delete (a dedicated single-order force-delete action). Access to force deletion is controlled by a new manager permission (orderForceDelete), so only authorised managers will see and use it.

• Three-State Trade Options in Symbol Group Profiles. Settings now support three states instead of a binary checkbox: "Allow", "Disallow" and "Use defaults". This means an override no longer becomes permanent once set — you can clear it from the UI at any time and fall back to the symbol's default.

  
• Improved MT5 Group Import. MT5 group imports now correctly preserve the source server's margin and stop-out settings: Open Position Type (Netting / Hedged), Stopout Value Type (Percentage / Money) and Margin Call Value Type (Percentage / Money).

Bug fixes

• Zero Volumes Now Accepted on MT5 Symbol Import. MT5 symbol and group imports no longer fail when VolumeMin, VolumeMax, VolumeStep, or VolumeLimit are set to 0 — the imported entity keeps the literal 0 value. The Symbols and Symbol Group Profile edit forms also accept 0 for the same four fields.

---

What's new

• We have extended the ApplyMinSpreadToTrades and ApplyMaxSpreadToTrades symbol parameters to support per-account and per-group overrides.
• We have added a new per-symbol parameter ThrottleBypass (in points) for MT5 Gateway and MT4 Bridge.

Misc

• TCP stats will work for older windows servers.

---

What's new

• We have extended the ApplyMinSpreadToTrades and ApplyMaxSpreadToTrades symbol parameters to support per-account and per-group overrides.
• We have added a new per-symbol parameter ThrottleBypass (in points) for MT5 Gateway and MT4 Bridge.

---

Misc

• We have improved how the LiquidityManager recovers from corrupt persistent delivery files.

---

Misc

• We have improved how the MatchingEngine recovers from corrupt persistent delivery files.

---

Bug fixes

• We have fixed an issue introduced in v26.4.83 where, after the MT5 ExternalOrderListener plugin migrated its configuration to a local file, all external order sender logins were rejected as "does not have permissions" once the plugin restarted.

---

Misc

• Diagnostic log when partial-fill volume is not a multiple of OrderSizeIncrement — Trade server now emits an error log when a liquidity provider reports a partial-fill cumulative quantity that does not align with the symbol's configured OrderSizeIncrement, recording the originator order id, symbol, the reported quantity and the adjusted value. Previously the alignment fix-up was applied silently, which could cause partial fills to be reported as full-order volume without any trace in the logs.
• Request id propagated through trading-engine logs — Order routing context metadata, including the originating client request id, is now threaded through the order-engine command pipeline and surfaced in the corresponding log lines for placement, modification, SL/TP modification, force-delete and stop/stop-loss/take-profit/stop-out trigger paths, so an individual client request can be followed end-to-end through all stages of order handling.
• PostgreSQL exporter and export persistence logging — The PostgreSQL exporter and the file-based export persistence layer now produce more detailed log output: table names are included in batch log messages, state-file save operations are confirmed in the log, and stream-level I/O failures are reported with their underlying error context, making export-pipeline issues easier to diagnose.
• 3rd party dependencies have been updated to the latest versions.

---

Bug fixes

• We have fixed an issue where margin was miscalculated for accounts which had pending orders actived then not filled and then cancelled

---

What's new

• We have added the ability to expand any row in the Markouts Report to display an inline Ticks Chart (Makers & Takers) directly beneath it, without leaving the report page. Multiple rows can be expanded simultaneously, each showing an independent chart.
  
  

Bug fixes

• We have fixed an issue where the Trace ID column was absent from the Trade Blotter exported file, even when explicitly selected in the UI.

---

Misc

• We have added performance monitoring feature to the plugin

---

Misc

• Saving artifacts to help with crash investigations