Release notes

Releases summary

What's new

• We have extended the FIX Server ExecutionDelay parameter to support multiple rules. A session or symbol can now apply different delay ranges depending on a FIX tag value (with * and ? wildcard matching), plus a single default delay for everything else. Existing single-range delays keep working unchanged.

  New / changed APIs

  • New: POST /api/v2/config/fix-session-set/profile/parameter/execution-delay — adds or updates the execution delay parameter using the new rule list (UpdateExecutionDelayFixSessionSetParameterCommandV2, carrying ExecutionDelayParameterV2 → ExecutionDelayParameterValueV2 → ExecutionDelayRuleV2 { minMs, maxMs, tag?, glob? }). Returns UpdateExecutionDelayParameterResponse.
  • Unchanged (v1): POST /api/v1/config/fix-session-set/profile/parameter/execution-delay continues to accept the single range ({ minMs, maxMs }).
  • Changed response (additive, v1): POST /api/v1/config/fix-session-set/profile/configuration now returns a new executionDelayRules field (the full v2 rule list) alongside the existing executionDelay (a single-range view projected from the default/catch-all rule).
  • Unchanged: the execution delay reset (.../parameter/execution-delay/reset) and delete (DELETE .../parameter/execution-delay) endpoints are version-agnostic and unchanged.
  • Note: the FIX Session profile controller now also serves its existing endpoints under /api/v2/... with behavior identical to /api/v1/....

---

What's new

  
• We have added a shared filter and period to dashboards. A dashboard can now drive the global filter and the time period for the reports shown on it, so you set them once and every report on the dashboard updates together.
  • Report pages you add to a dashboard use its shared filter and period automatically. Their own filter and period controls are hidden, and they open already showing the dashboard's selection — no flash of their own controls first.
  • The Market Watch and Open Positions widgets follow the dashboard's shared global filter too, and re-load when it changes.
  • Any widget can opt out. Turn on "use this widget's own filter and period" to let it keep its own selection instead of the dashboard's.
  • A dashboard shows only the controls its widgets actually use — the global filter, the period, both, or neither.
  • Your dashboard selections are remembered across reloads and stay separate from what each standalone report page remembers, so choosing a filter on a dashboard never changes a report page's own last-used filter.
• We have also given the inline global filter and period controls a cleaner look by removing their text labels.

---

What's new

• Larger page sizes for REST query endpoints — The maximum number of results per request has been raised across the admin API — up to 10,000 trading accounts, 1,000 clients, 1,000 permission sets, 1,000 symbols, and 250 groups — and the public Get Symbols endpoint now returns up to 1,000 symbols per request.
• Configurable FIX connector order-execution timeout — Added a configurable per-session order-execution timeout to the FIX connector (OrderExecutionTimeout, default 30 seconds). When a liquidity provider accepts an order but sends no execution report within the timeout, the connector now cancels the in-flight FOK/IOC order and frees the position, instead of leaving it locked as "being executed" until the provider replies or the session restarts.

Bug fixes

• The FIX market-data connector no longer drops a live subscription when a late rejection arrives for a request that was already superseded by re-subscribing the same symbol, which previously left that symbol without quotes.
• Automated per-IP rate-limit bans (HTTP 403) now expire after the configured reject interval, instead of persisting until the server is restarted — which previously could block REST access for every client sharing an egress IP behind a proxy or load balancer.
• Scheduled backups now run at every configured interval; certain start-offset and interval combinations previously caused some runs to be skipped silently, so backups ran less often than configured.
• Minor bug fixes and improvements.

Misc

• Logging — Admin configuration changes are now recorded in the audit log with the originating client IP — read from the X-Forwarded-For header for deployments behind a reverse proxy or load balancer — along with optional caller-supplied trace, application-name, and application-version headers for request correlation.

---

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

---

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

---

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.

---

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

• Improved MT5 migration flow in the Groups page, with better status indicators (Ready / Blocked), expandable error details, and blocking validation for missing required fields.
• MT5 Trading Account migration now reads the Client column from the CSV and stores it as clientExternalId on the created client record.
• Monetary values in data grids are now colored green when positive and red when negative. All price and money columns are right-aligned in a monospace font for easier scanning.
• WebSocket connections now retry indefinitely with capped exponential backoff (~2–32s with ±20% jitter) instead of stopping after 3 attempts. Token refresh is also synced and the WebSocket module now picks up the updated token after a /refresh for all subsequent messages.
• Auto-logout error message text and styling have been updated. Now it contains the real reason of logout.
• Login screens now show product-specific headings: "Admin Portal" for the admin app and "Web Trader" for the terminal.

Bug fixes

• Fixed a bug where client initials were not displaying correctly in the user avatar component, which caused an error in the UI.
• Stop Limit orders in the Admin UI can now be placed and modified with Limit Price on either side of Stop Price, matching actual API behaviour.
• Fixed a duplicated column name appearing in the Order Routing Rules grid.
• Fixed a validation error that incorrectly blocked cloning a Manager group (Managers/…) into a group with a non-manager name (and vice versa).

---

What's new

• We have added the ability to send a client's account group name in the Account field (tag 1) of orders forwarded to a liquidity provider. LPs that expect a string identifier now receive it directly, with a single configuration parameter and no duplicate tag

---

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.

---

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.

---

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.

---

Bug fixes

• We have fixed an issue where, after a temporary floating-leverage margin rule expired, an affected position's margin could stay elevated — or even increase — instead of returning to its normal level. Margin now correctly reverts to
  the original rate when the rule's interval ends

---

What's new

• We have added an opt-in performance diagnostics parameter to the MT5 DataWarehouse plugin that logs per-hook latency on demand, helping diagnose throughput issues without impacting normal operation when disabled.

---

Misc

• Saving artifacts to help with crash investigations