Help Center
Our products knowledge base for customers
Order issues
Order issues
The Order issues tab of the Daily operations section displays the registry of order issues. It contains provider messages the platform could not apply (for example, an execution for an already closed or unknown order, a duplicate execution, a provider's refusal to cancel an order that is already in a final status on its side), as well as stuck, stopped and mismatched client and provider orders that the system finds by itself.
The tab is available with the Manage orders permission in the user's role. The number of open rows is displayed next to the tab name: in red if there are Critical rows among them, otherwise in orange.
Please note! OpenCriticalandWarningrows do not allow closing the day. For more details, see theClosing the daysection of this article.
![]()
Row counters by severity (Severity) are displayed above the table: Open - all open rows, Critical, Warning and Info - by severity, Acknowledged - how many of them have been taken into work.
Registry table
One registry row is one issue of one type for one order (for provider messages - for one of its executions). If the same issue repeats, no new row is created - the Occurrences counter of the existing row grows, and its severity can only increase.
The table contains the following fields:
| Name | Description |
|---|---|
| ID | Registry row number |
| Severity | See the Severity section |
| Status | See the Statuses section |
| Issue type | Issue type, see the Issue types section |
| Broker | Broker the row relates to |
| Account | Account the issue relates to. May be empty if the provider sent a message for an order the platform did not recognize |
| Order ID | Order the issue was detected for |
| Client order | Client order linked to the provider order |
| Connector | Connector the provider message came through |
| Detail | Short description of the issue |
| Occurrences | How many times the issue has been detected. For rows with the Detector source - the number of checks at which the issue was found |
| First detected | When the issue was detected for the first time |
| Last detected | When the issue was detected for the last time |
| Source | Where the issue was detected: Trading engine - while processing the order, Connector proxy - when calling the connector, Detector - during the automatic check, Dead letter - a provider message that did not reach the order |
The table can be filtered by Severity, Status, Issue type, Connector, Account, Order ID, Issue IDs and the Detected period. The Open only switch leaves only open rows (New and Acknowledged); it is off by default, and the table displays rows in all statuses.
The table can be sorted by ID, Severity, Status and Last detected, and saved by clicking the Save as XLSX button.
Severity
| Name | Description |
|---|---|
| Critical | Real funds are affected: a provider execution has not been booked or has been booked incorrectly. A notification is sent, the row does not allow closing the day. |
| Warning | The status or quantity of the order in the platform differs from the provider or the client order, but the trades have been booked correctly. |
| Info | Information for reference. No notification is sent, the row does not prevent closing the day. |
Statuses
| Name | Description |
|---|---|
| New | A new row. A closed row also returns to this status if the issue repeats, as well as a row reopened with the Reopen button |
| Acknowledged | The row has been taken into work. It remains open: notifications keep coming for it, and it does not allow closing the day |
| Resolved | The issue is resolved: manually with the Resolve button, with an action from the Fix menu or automatically when the system no longer sees the issue. If the issue repeats, the row returns to the New status. For types that close by themselves, this happens at the next check if the issue persists: such a row cannot be removed with the Resolve button - fix the issue or ignore the row |
| Ignored | The row has been ignored with the Ignore button. While the issue persists, the row is not reopened (unless its severity increases), no notifications are sent for it, and it does not prevent closing the day. For types that close by themselves, the row moves to the Resolved status when the issue is resolved; rows of other types remain Ignored |
Issue types
The default severity and the Fix menu actions are given for each type. The system checks types marked in the Closes by itself column automatically and moves the row to the Resolved status when the issue is gone. Other rows are closed only manually or with an action from the Fix menu.
Provider messages for an unknown or closed order
| Name | Description | Severity | Closes by itself | Fix actions |
|---|---|---|---|---|
| Execution for unknown order | The provider sent an execution report for an order that does not exist in the platform | Critical if the report contains an execution, otherwise Warning | no | Apply execution, Mark as duplicate, Load trades |
| Unknown order ID | The connector did not recognize the Order ID in the provider report | Critical if the report contains an execution, otherwise Warning | no | Apply execution, Mark as duplicate, Load trades |
| Execution for terminal order | The provider sent a report for an order that is already in a final status in the platform (Executed, Cancelled, Rejected, Expired) | Critical if the report contains an execution, otherwise Warning | no | Apply execution, Mark as duplicate, Load trades |
| Execution for stopped order | The provider sent a report for a stopped order | Critical if the report contains an execution, otherwise Warning | no | Apply execution, Mark as duplicate, Reject order, Cancel at provider, Load trades |
| Execution in non-handling state | The provider report arrived when the order could not process it and was not applied. For example, the order was waiting for the trading session to start or for the connector to connect | Critical if the report contains an execution, otherwise Warning | no | Replay to engine, Mark as duplicate, Load trades |
| Execution for older attempt | A provider report (not an execution) for a previous version of the order after it was modified | Info | no | Replay to engine, Mark as duplicate, Load trades |
| Proxy event without client order | An event for a provider order arrived in the platform, but the client order no longer exists: the client trade will not be created automatically | Critical if the event contains trades, otherwise Warning | no | Link trades, Load trades |
| Provider message processing failed | The provider message could not be applied because of an error | Critical | no | Replay to engine, Mark as duplicate, Load trades |
Cancellation and orders that may remain active at the provider
| Name | Description | Severity | Closes by itself | Fix actions |
|---|---|---|---|---|
| Cancel reject with final status | The provider rejected the cancellation or modification of the order and reported that the order is in a final status on its side. The platform closed the order with the Rejected status based on this answer, but the status is not confirmed by the provider: the order may remain active at the provider. You can check this and cancel the order if necessary with the Cancel at provider action | Critical | no | Cancel at provider, Load trades |
| Cancel reject for unknown order | The provider rejected the cancellation of an order that is not being processed in the platform | Warning | no | Load trades |
| Final locally, live at provider | The order is closed in the platform, but there is no final answer from the provider for it. Warning - the connector disconnected while the order was waiting for its answer, and the order was rejected in the platform: only its previous attempt may remain at the provider. After reconnection, the status at the provider is not checked automatically: if the provider sends a report for the order, it will appear in the table as an Execution for terminal order row | Critical; Warning if the connector disconnected | no | Cancel at provider, Load trades |
| Synthetic reject after gRPC failure | The connector did not answer a request for the order, and the platform completed the request by itself: a new order is rejected, a cancellation or modification is refused. The request may still have reached the provider, and the order status there may differ | Warning; Critical if a cancellation or modification failed | no | Cancel at provider, Load trades |
| Possible duplicate live order | The order has been sent to the provider again, while the previous attempt may remain active at the provider | Warning | no | Cancel at provider, Load trades |
| Pending new resent after restart | After a platform restart, an order in the Pending status has been sent to the provider again, while the previous attempt may have reached it | Warning | no | Cancel at provider, Load trades |
Stuck and stopped orders
| Name | Description | Severity | Closes by itself | Fix actions |
|---|---|---|---|---|
| Stuck pending | The order has been in a pending status for too long: Pending, Pending replace - more than 2 minutes, Pending cancel - more than 1 minute. This includes a manual order waiting for the dealer's decision in the Dealer section | Warning, after 15 minutes - Critical | yes | Cancel at provider, Reject order |
| Order stopped | The order has been stopped and requires manual intervention | Critical if the order has executions or was pending cancel or modification, otherwise Warning | yes | Reject order, Cancel at provider |
| Active in DB without engine state | The order is not in a final status, but the platform does not process it: provider answers for it are not applied | Critical | yes | Reload order state |
Quantity and status mismatches
| Name | Description | Severity | Closes by itself | Fix actions |
|---|---|---|---|---|
| Client/provider status mismatch | The client and provider orders are in different statuses | Warning | yes | Fix order state, Reject order |
| Client/provider quantity mismatch | The client and provider orders differ in the executed quantity | Critical | yes | Fix order state, Reject order |
| CumQty regression | The executed quantity of the order at the provider does not match the platform. Critical - the provider reported an executed quantity smaller than the one already booked: the trade is booked for the quantity of the last execution. Warning - the executed and leaves quantities in the provider report do not add up to the order quantity | Critical or Warning | no | Cancel trades, Fix order state, Load trades |
| Overfill | The executed quantity at the provider exceeds the order quantity | Critical | no | Cancel trades, Fix order state, Load trades |
| CumQty and trades mismatch | The executed quantity of the order is not equal to the sum of the quantities of its trades | Critical | yes | Cancel trades, Fix order state, Load trades |
Trades and duplicates
| Name | Description | Severity | Closes by itself | Fix actions |
|---|---|---|---|---|
| Duplicate remote execution ID | A repeated provider execution. Warning - the platform did not book the repeated execution received from the provider. Critical - the execution has been booked on the account twice | Warning or Critical | Critical only | Warning: Mark as duplicate; Critical: Cancel trades |
| Unprocessed trade | The trade has been executed but not booked to the account - the same as in the Unprocessed trades tab | Warning, after 15 minutes - Critical | yes | Retry unprocessed trade, Cancel unprocessed trade, Mark as duplicate |
| Execution DB write failed | The execution could not be written to the system | Critical | yes | Retry failed execution, Cancel failed execution |
| Provider fill without client trade | There is a trade on the provider account for a client order, but there is no trade on the client account | Info | yes | Link trades |
| STP touch not applied | There is a touch rule for the STP trade, but the client trade has not been created | Info | yes | Retouch trade, Link trades |
Row sidepage
Clicking a row opens the Order issue sidepage with the row number:
![]()
The top of the sidepage shows the severity, status and type of the row, with the issue description below them. Further down, the sidepage displays:
- row data:
Source,Occurrences,First detected,Last detected,Last notified(the last notification),Broker,Account,Order ID,Client order, and, if available, the connector, the provider order ID and execution ID (Remote execution ID; the field has the same name in the accountExecutionstab) and the linked trade (Linked trade) created with a registry action; Context- additional parameters of the issue, for example the order status, type and quantities;Provider message- the original provider message. The block can be collapsed, the Copy button copies the message;Resolution- when and by whom the row was closed (Resolved at,Resolved by), and theComment;History- the history of statuses and actions:Time,Actions,Status,Member,Description. Records made by the system itself are displayed with the "—" member: "auto-resolved" - on automatic closing, "re-opened" - when the issue repeats.
The sidepage of a closed row:
![]()
The row sidepage also opens from an Order issue notification; a digest notification opens the Order issues tab.
Row actions
The status buttons and the Fix menu are located at the bottom of the sidepage.
Status buttons are displayed only if they are available in the current row status:
- Acknowledge - take a new row into work;
- Resolve - close the row as resolved, a comment is required;
- Ignore - ignore the row, a comment is required;
- Reopen - reopen a closed or ignored row.
The Fix menu contains the actions that fit the row type (the Fix actions column in the Issue types section). If an action cannot be performed now, it is displayed in gray, and a tooltip with the reason appears on hover:
![]()
For some types, the menu displays the Request status action (requesting the order status from the provider). It is currently unavailable.
Selecting an action opens a window with the action fields and the Comment field; actions that book or cancel trades and orders are highlighted in red. After a successful action, the Action applied notification appears, and the row moves to the Resolved status. The Load trades, Replay to engine and Cancel at provider actions move the row to the Acknowledged status: the result will come from the provider. The system will close a row of a type that closes by itself when the issue is resolved; a row of other types must be closed with the Resolve button after checking the result, otherwise it does not allow closing the day.
The Manage orders permission is sufficient for all registry actions.
| Name | Description |
|---|---|
| Apply execution | Book the provider execution: creates a trade on the provider account and the linked client trade. The Client account field allows you to specify the account of the client trade; if the field is empty, the account of the client order is used. The Skip margin check checkbox books the trade without a margin check |
| Mark as duplicate | Close the row as a duplicate if a trade with this Remote execution ID is already booked on the account |
| Replay to engine | Apply to the order again a provider message that was not processed. Available if the order is not in a final status |
| Reject order | Reject the order. If the order has been sent to the provider, a cancel request is sent to it first, and the order gets the Rejected status after the cancellation is confirmed |
| Cancel at provider | Send the provider a cancel request for the order regardless of its status in the platform |
| Reload order state | For an Active in DB without engine state row: restore the order state from the history of its executions, after which the platform accepts and applies provider answers for it again |
| Retry unprocessed trade | Book a trade that has been executed but not booked to the account. If the trade is already booked, the row is simply closed; if the trade cannot be booked, an error with the reason is displayed |
| Cancel unprocessed trade | Refuse to book the trade: the trade will not be booked to the account |
| Retry failed execution, Cancel failed execution | Write again an execution that could not be written to the system, or cancel it |
| Link trades | Create a client trade for a provider trade. Specify the Client account, Provider trade IDs (the provider trade identifier) and, if necessary, Skip margin check |
| Retouch trade | Apply the touch rule to the STP trade again |
| Cancel trades | Cancel the extra trades. The Trades to cancel field in the action window displays the trades of the account: for Duplicate remote execution ID - with the same execution ID, for other types - the trades of the order. Select the extra ones with checkboxes; only the selected trades are cancelled, the linked client trades are not cancelled. A comment is required |
| Fix order state | Bring the executed quantity and status of the order in line with the sum of its trades. Available only if the order is in a final status (Executed, Cancelled, Rejected, Expired) |
| Load trades | Load provider trades for the Period through the STP connector. If the period is not specified, the day of the row is used |
Please note! It is recommended to resubmit and cancel unprocessed trades and executions that could not be written to the system (Unprocessed trade,Execution DB write failed) after consulting Unity support. If the trade or execution is still not booked after resubmission, contact support.
Restrictions:
- Apply execution is available only for an execution with a provider ID on a provider account of the broker (except nominal accounts) and for an order that does not exist in the platform or is in a final status. The action is unavailable if a trade with this execution ID is already booked, if the trade would exceed the order quantity, and for a provider message about cancelling or correcting an already booked trade.
- Replay to engine is available only for an order that is not in a final status. For an order in a final status, Apply execution is used.
- A
Duplicate remote execution IDCritical row and aCumQty and trades mismatchrow cannot be ignored or marked as a duplicate: cancel the extra trade or bring the order in line with its trades (Fix order state). - Reject order is unavailable while the order is waiting for the provider's answer to a cancellation or modification.
- Cancel trades does not cancel swap trades and trades in a closed day.
Example: duplicate execution
A Duplicate remote execution ID - Critical row means that one provider execution has been booked on the account twice. To process it:
- Open the row and select Cancel trades in the Fix menu. The
Trades to cancelfield displays all trades of the account with this execution ID: ID, time, side, amount and price. - Select the extra trade, enter a comment and confirm the action. The row moves to the
Resolvedstatus immediately. - If after the cancellation the executed quantity of the order no longer matches the sum of its trades, a
CumQty and trades mismatchrow for this order will appear at the next check. Select Fix order state for it.
If it is unclear which of the trades is extra, contact Unity support.
A Duplicate remote execution ID - Warning row means that the repeated execution was received by the system and was not booked: funds are not affected. If a trade with this execution ID exists on the account, close the row with the Mark as duplicate action; otherwise - with the Resolve or Ignore button with a comment.
Automatic check
The system regularly checks orders and trades for the last 3 days: stuck orders, unprocessed trades and executions that could not be written - once a minute, the rest (stopped orders, mismatches between client and provider orders, mismatches between executed quantity and trades, duplicates) - once every 5 minutes. A found issue appears in the registry with the Detector source. When the issue is resolved, the system moves the row to the Resolved status.
The 3-day limit applies only to finding new issues. The system rechecks already open rows by their order or trade regardless of the date, so a row for an old order also closes by itself when the issue is resolved.
Please note! In one check, the system adds no more than 500 new rows to the registry. If there are more issues, the rest will appear at the next checks as the rows are processed, so the number of rows in the registry may be smaller than the number of issues.
Closing the day
In the Status tab, the registry is displayed as the Order issues operation with the number of open Critical and Warning rows (in the New and Acknowledged statuses). This operation cannot be processed with a button - the rows need to be processed: fixed, closed or ignored.
While there are such rows, the following are unavailable:
- Close day on accounts;
- Close day finally in the broker profile;
- automatic day closing configured in the
Automatizationsubsection: at the scheduled time the day is not closed, and anErrornotification of theEODrule group arrives with the error message set in the settings and the reason.
Important! All open rows of the broker are counted, regardless of the selected date and the account filter. An open row for one account does not allow closing the day on any account of the broker.Inforows, as well as rows in theResolvedandIgnoredstatuses, do not prevent closing the day.
Closing the day requires the Manage EOD permission, and processing registry rows requires Manage orders. Without the Manage orders permission, the number of open rows is visible in the Status tab, but the Order issues tab is unavailable and the operation name does not open it.
Notifications
For new Critical and Warning rows and when the severity of a row increases, Order issue notifications are sent in the Trading errors rule group. The notifications are received by members with access to the row's account according to the group setting for access sets. Rows without an account are visible only in the Order issues tab, the broker does not receive notifications for them. The notification contents and sending rules are described in the Order issue section of the template catalog.