Release notes

Releases summary

What's new

• Trading Account Events export — The PostgreSQL export pipeline now supports a trading_account entity that streams account lifecycle events — creation, every modification, and deletion — into a trading_account_events table. Each row carries the account's full current state with a version counter, so the complete history of an account can be reconstructed from the log.
• Export buffer upgrades on start-up (admin) — On every start, before any pipeline comes up, the server brings leftover export buffer files up to the record layout of the running release, so buffered records survive an upgrade. A file that cannot be upgraded is named in the log and left byte for byte as it was. 
• Export initialization permissions (admin) — Added four manager permissions covering the initialization of exports: initializeSymbolExport, initializeTradingAccountExport, initializeClientExport and initializeGroupExport.

Bug fixes

• The export queue no longer treats a corrupted segment as permanently backlogged, which had biased the pipeline toward writing later records to disk for the life of the process.

Misc

• The exporter now reports how many records were actually lost from a corrupted buffer file, instead of reporting the segment's full capacity.
• Logging — Export log messages now carry a consistent prefix identifying the database side, the local buffer files, or the start-up buffer upgrade, and a skipped-records line is emitted at error level. The export setup guide documents each message, its meaning, and the operator action it calls for. 

---

What's new

• MT5 symbol import now sets the Maximum Price Filter to the system default (1 000 000) when the MT5 PriceLimitMax is 0, instead of importing 0.
• Liquidity connectors now expose the optional Order Execution Timeout session parameter (milliseconds, 1..3600000), including a new column in the connectors grid.

• The SL/TP cells of open positions and working orders turn orange when they are within 10 pips of the live market price and red when they are within 5 pips.

  

Misc

• The grids on the 'Trade History', 'Order History', 'Cash Transfers' and 'Charts' pages now default to displaying a one-month date range (the same calendar day as today, but one month ago). This was done to speed up the initial loading time for pages with a large amount of data.

---

Bug fixes

• We have fixed an error when importing a bridge profile for a client whose matching engines have virtual liquidity pools with the same id. The import reported that a symbol was not found in the liquidity pool, and could also record the wrong matching engine for a symbol.

---

Bug fixes

• We have fixed a problem that stopped clients who trade only through FIX servers from running reports. Report symbols on a custom role could only be granted against an MT4 or MT5 server, so those clients had no way to give a role any symbol access, and every report failed with "At least one symbol should be selected". A role's report symbols can now be set to apply to any server.

---

Bug fixes

• We have corrected the handling of text values that exactly fill their allotted storage — logins, symbol names, comments, group and account names, and MT server names. Such a value could previously lose its final character, or be stored differently, depending on which platform the component was running on. These values are now stored complete and identically everywhere.

---

Bug fixes

• We have corrected the handling of text values that exactly fill their allotted storage — logins, symbol names, comments, group and account names, and MT server names. Such a value could previously lose its final character, or be stored differently, depending on which platform the component was running on. These values are now stored complete and identically everywhere.

---

Bug fixes

• We have corrected the handling of text values that exactly fill their allotted storage — logins, symbol names, comments, group and account names, and MT server names. Such a value could previously lose its final character, or be stored differently, depending on which platform the component was running on. These values are now stored complete and identically everywhere.

---

Bug fixes

• We have corrected the handling of text values that exactly fill their allotted storage — logins, symbol names, comments, group and account names, and MT server names. Such a value could previously lose its final character, or be stored differently, depending on which platform the component was running on. These values are now stored complete and identically everywhere.

---

What's new

• We have added a new CROSSx ECN liquidity provider connector, enabling crypto market-data consumption and Market/Limit (IOC/FOK) order routing over FIX 4.2.

Bug fixes

• We have corrected the handling of text values that exactly fill their allotted storage — logins, symbol names, comments, group and account names, and MT server names. Such a value could previously lose its final character, or be stored differently, depending on which platform the component was running on. These values are now stored complete and identically everywhere.
• We have fixed a crash where a liquidity provider session configured with an unreadable SSL certificate, CA file or private key would terminate the whole Liquidity Manager at connector start.

Misc

• We have added four new Liquidity Manager configuration parameters that control the size of the internal per-worker queues and buffer pools: WorkerShardCapacity (default 1024), LpDataPoolCapacity (default 1024), TradeRequestPoolCapacity (default 512) and TradeRequestV2PoolCapacity (default 128).
• We have improved how the xOpen Hub connector handles symbols that have no lot size configured. 

---

Bug fixes

• We have fixed an issue where floating leverage rules scheduled across the trading week (for example Sunday 21:10 → Friday 19:59) could fail to apply for the first minutes after their start time, and could apply their end-of-period leverage change at the wrong time. Such rules now activate exactly at their configured start and revert at their configured end.

---

What's new

• We have greatly improved processing performance and reduced memory consumption

---

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.

---

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.

---

Misc

• Saving artifacts to help with crash investigations