Release notes

Releases summary

What's new

• We have added support for string trading accounts (for example ECN_3006540_3) in the per-login hedging multiplier settings of a FIX session, not just numeric logins. This is a new v2 of the hedging endpoints. v1 keeps working for numeric logins; its read leaves out string accounts, which it cannot express.

  New endpoints:

  POST /api/v2/config/fix-session/hedging
  PUT /api/v2/config/fix-session/hedging

• We have added support for guaranteed delivery (order recovery) of execution reports to MT5 Gateways.

Bug fixes

• We have fixed FIX session set profiles leaving the FIX server listed on the matching engine after a symbol was deleted or moved to another pool. A moved symbol could also lose its place in the new pool, so orders through that pool could expire. 
• We have fixed the Country condition of the Execution Price Bands parameter. You can now add two spellings of one country to the same rule, such as "Pakistan" and "pakistan", or "Russian Federation" and "Russia".

Misc

• We have improved how long-running operations are shown. While the page is busy, the browser tab now shows a spinning Your Bourse icon and the progress in the tab title, such as "(42%)". You can switch to another tab and still see that the operation is running and how far it got.

---

What's new

• Order and position filters in Trade History (admin) — The admin Trade History report now accepts orderIds and positionIds filters, returning the trades of the listed orders or positions. A position reversal is returned for both the position it closed and the position it opened. 
• Market-data delay in Get Symbol — Each group's market-data delay is now resolved per symbol, and the public Get Symbol endpoint returns the resulting delay for the requesting client's group in whole minutes (dlyI), present only when a delay applies. 
• Transfer timestamp no longer required (admin) — The admin transfer request no longer requires the t field; requests that still send it are accepted and the value is ignored. 

Bug fixes

• Minor bug fixes and improvements.

Misc

• Logging — Request trace information is now logged consistently for rejected requests across all request types, and the first X-Forwarded-For address recorded in the audit log may now include a port, which is ignored.

---

Misc

• 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.

---

Bug fixes

• We have fixed per-account hedging multipliers on FIX sessions that send the client account as text: a rule set for a numeric account now applies to that account's orders, whichever account format the session uses.

• We have fixed a rare issue in the FIX server where deleting a FIX session while another configuration change to it was in progress could prevent a session with the same SenderCompID from being added again until the server's files were cleaned up manually.
• We fixed a rare FixServer crash when an STP endpoint was removed through the configuration API. The same crash could happen in other components when a connection to the Data Collector was closed.

Misc

• We have improved the speed at which incoming FIX messages are parsed, and we have tightened the validation of numeric, date and time fields so that values outside the FIX data types are refused instead of being silently reinterpreted.

---

Bug fixes

• We fixed Liquidity Manager leaving a connector stop request unanswered when it was shut down before the connector had finished stopping; the request is now answered and Liquidity Manager exits.
• We fixed crashes of Liquidity Manager and Matching Engine when a configuration client connected during shutdown or dropped its connection while a response was being sent
• We fixed a rare LiquidityManager crash when an STP endpoint was removed through the configuration API. The same crash could happen in other components when a connection to the Data Collector was closed.

Misc

• We have improved the speed at which incoming FIX messages are parsed, and we have tightened the validation of numeric, date and time fields so that values outside the FIX data types are refused instead of being silently reinterpreted.

---

Bug fixes

• We have made multiple fixes for batch configuration commands
• We fixed a rare Matching Engine crash when an STP endpoint was removed through the configuration API. The same crash could happen in other components when a connection to the Data Collector was closed.

---

Bug fixes

• We have fixed an issue where a slow Open Position Reconciliation or Maker Open Positions report could be cancelled by auto-refresh, leaving users with a misleading “No Rows to Show” message. The report now shows a loader until the data arrives.

Misc

• We have added automatic five-second updates to dashboard Tick Comparison widgets for periods ending at now. Historical periods remain unchanged.

---

What's new

• Throttling property in the Symbol edit form>Common tab now accepts a whole number from 0 to 1000. Set it to 0 to disable throttling.

Bug fixes

• The search function, which had been missing from the Trading Accounts and Managers pages, has now been restored.
• If the date is in the wrong format during MT5 data migration (for example, a year with two digits instead of four), an error message will now be displayed.
• The unclear error toast has been replaced with a modal window that offers action options (like overwrite or load the latest changes) in case multiple users edit liquidity providers simultaneously.
• A bug that caused the place order form to freeze in the loading state if the user did not have one of the default symbol pairs has been fixed.

---

Bug 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.

---

Bug fixes

• We have corrected Floating Leverage margin for rules that apply only to new positions, so closes, overlapping rules and account leverage changes now charge the intended margin on MT4 and MT5. We have also made MT4 keep the intended margin across a restart and partial closes, and rule identities now survive configuration saves.

---

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 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