Release notes
MT5 Gateway
26.11.135
04 Nov 2026Bug fixes
- We have introduced more accurate request times in the Trade Execution report for MT4, MT5 and FIX trades. The request time is now when the trading platform received the request, so Execution Duration includes any execution delay.
- We have fixed a rare crash or hang of the MT5 Gateway that could occur while the gateway was being stopped.
26.10.133
29 Oct 2026Bug fixes
- We have fixed Close By so that, when per-position hedge mode is enabled, the remaining position keeps its correct A-book/B-book split and no unnecessary hedge order is sent to the liquidity provider.
- We have introduced safer connection cleanup when a matching engine is unavailable, preventing a rare bridge or gateway crash during shutdown or reconnection.
26.10.132
23 Oct 2026Misc
- We have aligned trace identifiers across our trade records, FIX drop copy and tracing: a trace id is now written as a 32-character hexadecimal value, so the id stored with a trade is the one used to look up that order's trace. Orders that still send the previous
sender_uniquetrace id format in FIX tag 820 continue to be accepted.
26.10.131
21 Oct 2026What's new
-
We have introduced a
LogToFilesetting. The components no longer write their own log files by default, which removes disk writes from the trading path. All messages still appear in the MT5 journal.
-
We have added the order number, originator ID and trace ID to the "Client price" and "Slippage absorption" log lines of the MT5 Gateway, so each line can be matched to its order.
Bug fixes
-
We have fixed the A-Book/B-Book split for orders divided across several liquidity pools: under partial hedging, every pool except the last now receives its correct hedged share instead of almost none.
-
We have fixed a rare crash in the MT5 Gateway that could occur when a matching engine was removed or the plugin was stopping while orders were being sent.
Misc
-
We have improved the MarketDataSnapshotInterval parameter in the MT5 Gateway so the configured interval is now applied exactly, e.g. 50ms. Previously it was rounded up to the next 100ms, so symbols already configured with a value that is not a multiple of 100 (such as 50 or 150) will receive more frequent price updates. Symbols without the parameter are not affected.
26.10.130
16 Oct 2026Misc
- We have improved the accuracy of MT5 trade reporting in the trade_execution table.
26.10.129
16 Oct 2026What's new
- We have reduced the time the MT5 Gateway spends writing its order and execution log lines, so orders and fills are processed faster under load.
Misc
- We have added the ability to change the address (host and port) of a matching engine already configured on the MT4 Bridge or MT5 Gateway. The bridge reconnects to the new address straight away, keeping that engine's name, priority, password and symbols.
26.10.128
15 Oct 2026Misc
-
We have added a configuration option that lets the MT5 Gateway skip writing its own separate log file, keeping all gateway messages in the MetaTrader journal and removing a source of order-processing delays under heavy load.
26.10.126
06 Oct 2026What's new
- We have introduced guaranteed delivery of ExecutionReports from the Matching Engine to opted-in consumers (first consumer: MT5 Gateway). Fills and cancels now survive a Matching-Engine ↔ consumer disconnect and process restarts instead of being silently dropped. Opt-in is per consumer via a new
GuaranteedDelivery.TargetIdsconfiguration list.
Misc
- We have improved how the MT5 Gateway checks requests while a symbol has no live price. It now uses the last price it received instead of querying the MT5 server, which removes delays to prices, order processing and execution reports during news events. We have added the parameter
LastPriceMaxAgeMilliseconds(global and per symbol, default 60000) to set how old that price may be.
26.10.125
01 Oct 2026Bug fixes
- We have fixed slippage absorption so the absorbed amount now always reaches the client's price, including with Best Execution and for loss protection on stop losses. Stop-loss and limit orders confirmed at their requested price are dealt at exactly that price, and absorption no longer takes a client's price improvement a second time when positive slippage is already capped.
- We have fixed an issue where a hedged order filled in several parts could be given MT5 deals that did not add up to the requested volume. Every fill, and any unfilled remainder at expiry or cancellation, now accounts for the order's full volume.
26.9.123
25 Sep 2026Misc
- We have introduced a new "Price source" log entry for every filled trade on MT4 and MT5. It identifies the account, the order and the originating order, and lists each individual price adjustment applied to the trade
together with its value, so a client price can be explained without reconstructing it by hand.
26.9.120
19 Sep 2026Bug fixes
- We have fixed an issue where accounts using a partial Hedging Multiplier could have slightly less volume sent to the A-book than configured. For example, a 0.30 lot GOLD trade at a 70% Hedging Multiplier allocated 0.20 lots to the A-book instead of 0.21. Allocation is now exact for every Hedging Multiplier and volume.
26.8.117
11 Sep 2026What's new
- We have introduced propagation of the trading account and group from the MT4 Bridge and the MT5 Gateway, so orders opened on MT4/MT5 now carry the client's login and group through to the liquidity provider.
- We have added the ability to configure execution volume bands (price-band markup) per client country: the
ExecutionPriceBandsparameter now accepts a#Countryqualifier, applied at execution time with priority account > country > group.
Misc
- We have changed the behaviour of the
ThrottleBypassparameter: setting it to0now disables the throttle bypass. Previously0meant "bypass the throttle on any price change", which effectively disabled throttling instead. To keep the bypass active, set a positive number of points.
26.8.115
27 Aug 2026Bug 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.114
21 Aug 2026What's new
- We have added a new parameter
EnforceSupportedFillTypes(default:true) which controls whether the MT5 Gateway rejects an order whose filling type is not permitted by the MT5 group or symbol settings. Setting it tofalselets
those orders through, and it can be applied globally or to an individual symbol.
- We have fixed a race in the MT5 Gateway where slippage absorption rules could log spurious
Price::operator-errors and silently skip absorption while a liquidity provider's top-of-book was being updated.
26.8.112
12 Aug 2026Bug fixes
- We have fixed an issue where changing or removing the global
ThrottleBypassandThrottlingIntervalsettings had no effect until the gateway was restarted. These settings now apply immediately, so market data throttling can be adjusted without downtime. - We have fixed slippage absorption so that it correctly applies to Stop-Loss, Take-Profit and Pending order triggers on B-book trades, and so that it works as expected on symbols with a contract size other than 1 (e.g. XAUUSD, indices).
26.8.111
07 Aug 2026Misc
- small logging changes
26.7.107
22 Jul 2026Bug fixes
- We have fixed an issue where a price level could remain stuck in the MT5 order book after a symbol configuration change, leaving a stale bid or ask visible to clients even though it no longer existed in the market. The affected symbol now rebuilds its book correctly instead of requiring a restart to clear.
26.7.106
17 Jul 2026Bug 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.
26.7.103
07 Jul 2026Misc
- We have added a per-symbol diagnostic parameter,
DebugPricing, that lets support log the exact order-book price updates the MT5 gateway sends to the MT5 server, to speed up investigation of pricing issues.
26.7.102
03 Jul 2026Misc
- We have introduced Prometheus thread metrics for MT5Gateway 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.
26.6.98
12 Jun 2026What's new
- We have introduced Virtual Groups — a new configuration concept that allows grouping individual accounts and native MT group patterns into named collections (e.g.,
@@VG_PREMIUM). Virtual Groups can be used in all existing group pattern fields across execution delay, hedging multiplier, slippage absorption, included/excluded groups, manual hedging, and virtual liquidity pool configurations, enabling flexible account targeting without restructuring native MT groups. - We have introduced an optional per-symbol setting that, when enabled, aggregates a partially-filled order's individual fills into a single volume-weighted execution before notifying the trading platform, instead of sending one notification per partial fill.
Bug fixes
- We have also corrected the applied-markup calculation so it is accurate for orders filled in fractional-lot pieces.
26.5.94
30 May 2026What's new
- We have added ability to add multiple logins when setting up hedging
Bug fixes
- We have fixed an issue with MaxSpread when execution is happening on different pool from a pricing one
Misc
- We have added diagnostic functionality
26.5.90
14 May 2026What's new
- We have extended the
ApplyMinSpreadToTradesandApplyMaxSpreadToTradessymbol 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.
26.4.84
30 Apr 2026Misc
- We have changed default order type from FOK to IOC for Stop loss, Take profit, Pending orders, Stop outs
26.4.80
15 Apr 2026Bug fixes
- We have fixed an issue were quotes with large volume were filtered out, possibly stopping price updates
26.4.76
03 Apr 2026Misc
- Reduced number of worker threads
- tick updates are being done in different threads (same number as worker threads)
26.3.74
01 Apr 2026Bug fixes
- We have fixed an issue were a tick from lower layers could appear as top of book
26.3.73
29 Mar 2026Misc
- We have added ability to match abook orders for infinite sizes
26.3.72
29 Mar 2026Bug fixes
- We have fixed a regression where markups stopped being reported
26.3.70
27 Mar 2026Misc
- We have made a change where Pending order cancelations are always processed immediatelly
26.3.66
18 Mar 2026What's new
- We have released "Conditional hedging" functionality
26.3.65
13 Mar 2026Bug fixes
- We have introduced new way of handling close by orders
26.3.64
10 Mar 202626.2.61
03 Mar 2026What's new
- Passing real OrderRejectReason from LP
26.2.58
26 Feb 2026Bug fixes
- We have fixed an issue where we were trying to access unitialised ApiData cell
26.2.54
18 Feb 2026Bug fixes
- We have fixed an issue where slippage absorbtion configuration changes were not saved