Release notes

---

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.

---

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 issue in the FIX server where two simultaneous changes to an account's hedging rule could leave a logged-on FIX session hedging that account's orders by the older value until the session logged on again.

• We have fixed an issue where, with guaranteed delivery enabled for a gateway, a quick reconnect could leave the gateway without execution reports until it reconnected again, or cause some reports to be skipped.

---

Bug fixes

• We have fixed the MaxSpread setting on the FIX Server so that it is applied to B-book trades again. A-book trades are not affected, as MaxSpread applies to B-book trades only.

Misc

• We have improved the accuracy of MT5 trade reporting in the trade_execution table. 

---

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 a race in the FixServer configuration API: saving the configuration from one admin connection while another admin connection changed it could fail with an error
• We have improved the stability of FIX sessions during configuration changes: updating a session's settings while it is receiving orders can no longer disturb the message currently being parsed.

---

What's new

• We have introduced a configurable write buffer limits that automatically disconnects slow consumers whose outgoing buffer exceeds the threshold, preventing unbounded memory growth on the server.

---

Misc

• We have improved startup diagnostics: when a configured host name cannot be resolved, the log now reports the DNS failure and the host name instead of a generic "invalid configuration" error.

---

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 two per-symbol Negative Spread controls to the FIX gateway - Negative Spread Protection and Negative Spread Markup - matching the equivalent MT5 behaviour. Protection rejects orders that would execute immediately against a crossed book (bid above ask), and Markup charges the crossing amount at fill. Both are off by default.

Bug fixes

• Fix for LastQty for drop copy sessions

---

Misc

• Minor logging changes

---

What's new

• We have added the MT5 Deal ID / MT4 Order ID to the FIX drop copy TradeCaptureReport on the Tapaas session, so clients can reconcile drop copy trades against their MT bridge feed.

Bug fixes

• We have fixed an issue where trade volumes on the FIX drop-copy feed were rounded down to whole lots. Fractional-lot trades (e.g. 0.1 lots) now report their correct volume in tag 32 (LastQty) instead of 0.

---

Bug fixes

• We have fixed an issue where cloning a FIX session in the Cloud UI produced a session whose extra parameters were saved but had no effect until the FIX Server was restarted. Cloned sessions now apply their parameters immediately.

---

What's new

• We have added a new SetAccountId configuration API command that updates a session's account ID at runtime without disconnecting the session.

---

What's new

• More transparent markup reporting — Taker markup is now reported as a detailed breakdown rather than a single combined figure. You can now see exactly how each markup was built up — including the price band, bid/ask side, and the minimum and maximum spread components — in your trade records and reporting. This gives you clearer visibility into how pricing is applied to every fill.

Misc

• More reliable trade reporting — We've improved how cancelled, expired, and rejected orders are cleaned up, eliminating occasional spurious warnings and making trade record reporting more consistent.
• We have improved how the FIX server handles the account/order/group tag on order entry: an overly long account or group value is now trimmed to fit rather than causing the whole order to be rejected, so affected orders are accepted and the related error is no longer written to the logs.

---

What's new

• We have introduced support for string-based trading account identifiers. Order flow now carries an alphanumeric account, order id, and group end-to-end (from the client FIX session all the way to the liquidity provider), instead of being limited to numeric logins, and brokers can now set hedging multipliers per string account.

---

Misc

• Internal release, no new functionality

---

Misc

• •  We have fixed an issue where a session-level MarketDataThrottling parameter on a quote session was applied as a single shared budget across every subscribed symbol. Each symbol now gets its own independent throttling budget derived from the session-level default

---

What's new

• We have added possibility to pass group names to Liquidity providers

---

Misc

• Log files have daily rotation

---

Bug fixes

• We have fixed an issue where changing a FIX session symbol's market data pool via the Configuration would silently stop market data flowing to the connected client.

---

Misc

• We have improved how the FixServer recovers from corrupt persistent delivery files.

---

Misc

• We have increased the maximum supported length of the FIX taker client_group name from 31 to 63 characters, so longer group names are no longer silently truncated and per-group markup overrides are applied correctly on every fill.

---

What's new

• We have added possibility to set markups and Min/Max spread per group (group information arrives in configurable tags)

---

Bug fixes

• We have fixed a potential stale price issue when Matching Engine gets disconnected