Release notes

Releases summary

Misc

• 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_unique trace id format in FIX tag 820 continue to be accepted.

---

Misc

• 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_unique trace id format in FIX tag 820 continue to be accepted.

---

Misc

• 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_unique trace id format in FIX tag 820 continue to be accepted.

---

Misc

• 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_unique trace id format in FIX tag 820 continue to be accepted.

---

Misc

• 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_unique trace id format in FIX tag 820 continue to be accepted.

---

Misc

• 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_unique trace id format in FIX tag 820 continue to be accepted.

---

Misc

• We have introduced faster ClickHouse log-file handling in the FixServer, which removes latency spikes when FIX message logging to ClickHouse is enabled.
• 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_unique trace id format in FIX tag 820 continue to be accepted.

---

Misc

• We have introduced faster ClickHouse log-file handling in the Liquidity Manager, which removes latency spikes when FIX message logging to ClickHouse is enabled.
• 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_unique trace id format in FIX tag 820 continue to be accepted.

---

What's new

• We have fixed Execution Duration for MT5 orders in the Trade Execution report and its API. It now includes the execution delay and the time in the Matching Engine, so B-Book orders no longer show 0–1 ms.

---

Bug fixes

• We have fixed the Symbols column in the A/B Book settings table for MT4 Bridge and MT5 Gateway. A rule saved with no symbols selected now shows "All Symbols", the same as a rule saved with "All" selected. Before, it showed an empty cell, which looked as if the rule applied to no symbols.

• We have fixed the permission check on the liquidity provider symbol import API. Importing symbol connector names and markups now needs the "Can configure liquidity providers" permission, as it already does in the portal. A user or personal access token with only "Can view liquidity providers" now gets 403 Forbidden.

  Breaking change: this endpoint now needs "Can configure liquidity providers" instead of "Can view liquidity providers":

  POST /api/v1/config/liquidity-provider/symbols/import

Misc

• We have improved the list of liquidity provider types by removing the LMAX, CFH and FXCM Demo FIX Connector types, which could no longer be set up. Clients approved as demo now get the same connector types as live clients. 

  The connectorType field no longer returns LMAXDemoFIXConnector, CFHDemoFIXConnector or FXCMDemoFIXConnector, affected endpoint:

  POST /api/v1/config/fix-session/maker

---

Bug fixes

• The public Get Symbol endpoint now returns the symbol configuration and ETag for the requesting client's own group, so clients in different groups, or a client whose account moves to another group, no longer receive another group's cached trade mode, order limits, margin rates or swaps.
• Admin collections for holidays, groups, clients, permission sets and liquidity connectors now report the same version on every API connection, so conditional requests no longer return a full response just because they were served by a different connection.
• Trade FIX connectors now close the session when the liquidity provider sends a message larger than 16 MiB, instead of buffering it without limit.
• The PostgreSQL export now stops with an error when the database returns an unexpected cursor value, instead of resuming from an invalid position.
• Minor bug fixes and improvements.

Misc

• Documentation — The API specifications now document ETag as an opaque validator that clients must send back unchanged and must not parse or treat as a version number. They also describe symbol and group mask syntax and matching rules consistently across all endpoints. The export setup guide has been reorganized around the Trade Server side.

---

What's new

• We have introduced a LogToFile setting. 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.

---

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.

---

Misc

• Saving artifacts to help with crash investigations