368
edits
Changes
no edit summary
The platform generates an alert if the limits of the OS, hardware, bandwidth, software and/or broker processing speed is reached.
== Trading system alerts ==
=== Order status is processed longer than xxxx ms — TR01 ===
The status of the order is being processed in the Trading Server longer than xxxx ms.
<br>
<br>
=== TR03 — order Order modification or cancellation is taking more than xxxx ms— TR02 ===
Message: The Modify Order command was pending for 2000 ms. Order ID: 22.
The broker API is unable to process your orders in a timely manner! Place/modify fewer orders and check your Internet connection.
In MultiCharts 14 we introduced the monitoring of the auto trading orders' speed from the moment of generation up to reaching the trading plugin. The monitoring is implemented by using test messages.
<br>The way that test messages perform is identical to the way that real orders follow in MultiCharts (from module to module). The only difference is that it is not sent to the broker plugin and to the broker itself. The test message is intended to determine the load on the info channels within the application and the performance of the system in general. If the test messages are delayed or failing it means that the load on the internal info channels is too high so it leads to the queue of orders and statuses where they are waiting to be sent and processed.
=== FS01 — long Long delay of the order display in the Order and Position Tracker (the delay exceeds xxxx ms)— FS01===
Message: The test message was delivered in the Order and Position Tracker window with a delay.
=== FS02 — order Order display failure in the Order and Position Tracker (the delay exceeds xxxx ms)— FS02===
Message: The channel of sending messages to the Order and Position Tracker window is blocked or the messages queue is too long for the test message to be handled within 2000 ms.
<br>
=== FS03 — heavy Heavy load on the order processing channel: processing is taking more than xxx ms— FS03===
<br>Message: The auto trading system test message for <instrument name> instrument has exceeded the timeout of 500 ms by 44. Possible reason: the system is overloaded with a high number of trading commands. Please try to reduce the number of charts with auto trading.
<br>
=== FS04 — order Order processing channel failure: processing is taking more than xxx ms— FS04===
<br>Message: The auto trading system test message for <instrument name> instrument exceeded the timeout of 1500 ms. The auto trading system may lose its functionality (the orders may not be delivered to the broker, or MultiCharts may not receive the order statuses from the broker). It is recommended to restart all MultiCharts processes.
=== FS05 — long Long delay in the calculation of studies (the delay exceeds xxxx ms)— FS05===
<br>Message: <Strategy name> (<instrument name>) strategy calculation start time lags behind the tick arrival time by xxx ms.
=== FS06 — study Study calculation overload: the load has exceeded the computer’s capability (the delay exceeds xxxx ms) — FS06===
<br>Message: <Strategy name> (<instrument name>) strategy calculation start time lags behind the tick arrival time by more than 27429 ms. Auto trading will be stopped.
<br>
=== FS07 — main Main process is not responding during xxxx ms — FS07===
<br>
=== FS08 — emergency Emergency shut down of StudyServer — FS08===