Release notes

Releases summary

Bug fixes

• A StopLimit order modification that supplies only one of the stop and limit prices is now rejected, instead of being accepted with the supplied price silently discarded. 
• Minor bug fixes and improvements.

Misc

• Logging — Order and position requests on both the client and admin APIs are now logged with their trace information: originating account, socket and forwarded IP addresses, and the caller-supplied trace code, application name and version.
• Documentation — The public API specification now documents the X-Forwarded-For, X-YB-TRACE-CODE, X-YB-APP-NAME and X-YB-APP-VERSION request headers.
•  Third-party dependencies have been updated to the latest versions.

---

What's new

• We have improved FIX server and bridge profile execution to apply matching engine configuration changes through batch API commands, reducing the number of individual calls per profile execution and improving reliability. 

• We have added support for FIX symbols whose quote and trade sessions use different virtual liquidity pools. Order prices are now validated against the quote session's pool while orders execute against the trade session's pool, removing the previous limitation that forced both to share a single pool.

---

Bug fixes

• We have fixed an issue where floating leverage symbol groups were ignored on servers whose configuration defines symbol groups but no floating leverage rules, and were dropped from the configuration file on the next rule change.

Misc

• Minor stability improvement

---

Misc

• small logging changes 

---

What's new

• We have greatly improved processing performance and reduced memory consumption

---

Misc

• We have improved the Trade Blotter report by splitting the "A-Book Quantity" column into two distinct columns: A-Book Quantity (Attempted) — the hedge size requested to the LP, and A-Book Quantity (Filled) — the actual volume filled by the LP. This makes it easy to identify rejected hedges where the attempted size is non-zero but the filled size is zero.

---

What's new

• We have added the MT5 Deal ID / MT4 Order ID to the FIX drop copy TradeCaptureReport on the Tapaas session, so clients can reconcile drop copy trades against their MT bridge feed.

Bug fixes

• We have fixed an issue where trade volumes on the FIX drop-copy feed were rounded down to whole lots. Fractional-lot trades (e.g. 0.1 lots) now report their correct volume in tag 32 (LastQty) instead of 0.

---

Misc

• We have improved liquidity-provider resilience: when a PrimeXM/PXM feed sends a quote update or withdrawal for a price we are not currently holding, the affected instrument is now re-synced on its own instead of dropping and reconnecting the entire liquidity-provider session. This removes the continuous reconnect loop seen with the PXM feed and keeps all other instruments streaming uninterrupted.

---

What's new

• The Journals page has been added to the Admin UI, allowing you to search through the server log. This feature is only available to managers with the View Logs permission.

  

---

Bug fixes

• We have improved MT gateway resilience so that a symbol's price stream to MT5 recovers automatically after the gateway briefly loses and re-establishes its matching-engine connection, instead of staying stuck until a gateway restart.

---

Bug fixes

• We have resolved the spurious error messages reported by the MT5 External Order Listener plugin when it runs on a History (non-main) server after an upgrade, and hardened plugin startup to prevent a crash seen in certain builds.

---

What's new

• We have added the ability to send a client's account group name in the Account field (tag 1) of orders forwarded to a liquidity provider. LPs that expect a string identifier now receive it directly, with a single configuration parameter and no duplicate tag

---

Misc

• We have introduced Prometheus thread metrics for  MT5Coverage,plugin. Component now collects per-thread latency histograms, memory usage gauges, and a component-level last_update timestamp, exposing them via the heartbeat response to the Configuration API every 5 seconds.

---

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.

---

Misc

• Saving artifacts to help with crash investigations