Release notes

Releases summary

26.9.1

07 Sep 2026

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.

Configuration and management portal https://yourbourse.cloud.

26.9.4

04 Sep 2026

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.


Reporting & Risk Management portal https://yourbourse.cloud.

26.9.2

04 Sep 2026

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.


26.8.115

27 Aug 2026

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.

26.8.115

27 Aug 2026

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.

26.8.115

27 Aug 2026

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.

26.8.115

27 Aug 2026

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.

26.8.115

27 Aug 2026

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. 

26.8.47

21 Aug 2026

What's new

  • Symbol permission filtering on the Symbol channel (admin) — The admin WebSocket Symbol channel now filters broadcasts by the subscriber's permissions: a subscriber receives symbol add, update and delete events only for symbols supported by the group of the trading account it is subscribed as. Group and trading-account channels apply the same permission check, and a change to a permission set, group or trading account is picked up immediately.

Bug fixes

  • A holiday whose symbol mask names a single symbol exactly now applies to that symbol. Holiday masks are matched against the symbol's full path, with the same wildcard, exclusion and first-match-wins rules used by symbol group profiles and group masks.
  • Transfers with the CreditBonus trade type are now accepted and adjust the account's credit. CreditBonus and stop-out credit adjustments are authorized by the credit-operations permission, in line with regular credit transfers.
  • Minor bug fixes and improvements.

Misc

  • Position corrections are validated against the account (admin) — Creating an open position is now refused when the account already holds a position on the instrument and the pair keeps a single net position — always on an exchange instrument, and on any instrument in a group configured for netting. A non-zero swap is refused on an exchange instrument, at create and at modify alike, and invalid input in the average open price, swaps, commission, fee, stop loss or take profit is reported as bad input rather than as an internal error.
  • Server-assigned liquidity connector identifiers (admin) — Adding a liquidity connector through the admin API now mints the connector identifier on the server and returns it in the response; an add that supplies a non-zero identifier, or an identifier already in use, is refused before the connector is constructed. 
  • End-of-day marker in the By Time order routing filter (admin) — The By Time filter now accepts 24:00:00 as an end-of-day marker for both the start and the end of the window, so a rule can cover the remainder of the day without losing the final second. Invalid times are now rejected when the routing configuration is loaded instead of being silently accepted. 
  • Correcting the commission or fee recorded on an open position no longer moves the account's daily and monthly charge totals, so the statement no longer disagrees with the balance in the period of the correction.
  • The By Time order routing filter now treats its window consistently as half-open — the start time is inclusive and the end time is exclusive — and a window whose start equals its end matches nothing.
  • Logging — Admin requests that create, update or delete a permission set, singly or in a batch, are now trace-logged. 

26.8.112

12 Aug 2026

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.

26.8.111

07 Aug 2026

What's new

  • We have greatly improved processing performance and reduced memory consumption

Support for margin accounts in MetaTrader 5 trading platform.

26.7.106

17 Jul 2026

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.

26.7.102

03 Jul 2026

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.

25.6.85

13 Jun 2025

Misc

  • Saving artifacts to help with crash investigations