894
edits
Changes
Jump to navigation
Jump to search
Message: The test message was delivered in the Order and Position Tracker window with a delay.
<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>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.<br>This alert appears when the first test message has completed its way in MultiCharts with a delay. The delay time is specified in the message. This warning means that orders/statuses start forming queues and this results in the delay in the order sending/status processing. It warns the user to be careful and to avoid creating more charts and other windows. That would increase the load on the computer and the trading system. It is recommended to restart MultiCharts.
<br>Message: <Strategy name> (<instrument name>) strategy calculation start time lags behind the tick arrival time by xxx ms.
=== FS07 ===
The main process is not responding during xxxx ms
<br>
Message: User Interface of MultiChart64. exe (PID = 19784) process is not responding. Last successful response time is xxx.
=== FS08 === Emergency shut down of StudyServer<br>Message: StudyServerStudy storage operation failure.exe has encountered an error. It is required to restart all platform processes for the proper operation of the studiesPlease reboot your machine.
The Fail-Watch alerts and trading system warnings were introduced in the frames of our new Fail-Watch system.
The platform generates an alert if the limits of the OS, hardware, bandwidth, software and/or broker processing speed is reached.
== Trading system alerts System Alerts ===== TR01 — order Order status is being processed in the Trading Server longer than xxxx ms — TR01 ===Message: The broker API status of the order is unable to process your orders being processed in a timely manner! Place/modify fewer orders and check your Internet connectionthe Trading Server longer than xxxx ms.
<br>
Message: The order status is delayed. Place/modify fewer orders and check your Internet connection. <br>[[File:TR01.png|400px500px]]
<br>
=== TR02 — order Order or OCO group placement is taking more than xxxx ms— TR02===Message: The placed OCO group timeout exceeded Broker Order IDs: ,2 pending for 2017 msplacement is delayed. It can be caused by an unstable Place/modify fewer orders and check your Internet connection to the broker’s servers. As a result, closing position and processing the orders can be delayed.
<br>
[[File:TR02.png|400px500px]]
<br>
=== TR03 — order Order modification or cancellation is taking more than xxxx ms— TR03 === Message: The Modify Order command was pending for 2000 mscancellation/modification is delayed. Order ID: 22.The broker API is unable to process your orders in a timely manner! PlaceCancel/modify fewer orders and check your Internet connection.
<br>
[[File:TR03.png|400px500px]]
<br>
== Fail-Watch alerts Alerts ==
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: High CPU load. The data on charts and in Order and Position Tracker is received with delays. Please decrease the number of trading charts.
<br>
[[File:FS01.png|400px500px]]
<br>
=== 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 High CPU load. No data is received on charts or in Order and Position Tracker window is blocked or the messages queue is too long for the test message to be handled within 2000 ms. Please stop auto trading and restart MultiCharts. <br>Possible reasons and recommendations:
# There are too many data updates in the Order and Position Tracker. This includes orders, positions, alerts, logs, etc. It is required to decrease the number of Order and Position Tracker windows, auto trading charts, open positions, orders, connected broker profiles and/or the number of alerts generated by the studies.
# Overall CPU load can also affect the speed of the info exchange through this channel. It is recommended to decrease the general load on the CPU or add more resources to your machine.
<br>
[[File:FS02.png|400px500px]]
<br>
=== FS03 — heavy High load on the order processing sending channel: processing is taking more than xxx the order hasn't been sent for xxxx ms— FS03=== <br>Message: High CPU load. Orders are sent and order statuses are received with delays.
<br>This alert appears when the first test message fails to complete its way in MultiCharts. If you receive this alert right after enabling auto trading, it means that the data channels are heavily loaded and the time required for an order to pass through MultiCharts exceeds the timeout. In this case, it is required to find out which component of MultiCharts impacts the overall load on the system and decrease the load. Often this alert appears on machines that do not meet the recommended tech specs or when one of the MultiCharts processes that are engaged in the order/status info exchange is frozen or finished.
<br>
[[File:FS03.png|400px500px]]
<br>
=== FS04 — order processing channel Order sending failure: processing is taking more than xxx the order hasn't been sent for xxxx ms— FS04=== <br>Message: High CPU load. Order placement commands are no longer processed on time. Please stop auto trading and restart MultiCharts.
<br>
[[File:FS04.png|400px500px]]
<br>
=== FS05 — long Long delay in the calculation of studies (the delay exceeds xxxx ms)— FS05=== <br>Message: The active strategy is being calculated with delays.
<br>This message is displayed if a strategy calculation time lags behind the arrival time of a tick which initiated the calculation.
<br>
[[File:FS05.png|400px500px]]
<br>
=== FS06 ===Study calculation overload: the load has exceeded the computer’s capability (the delay exceeds xxxx ms)— FS06=== <br>Message: <Strategy name> (<instrument name>) There was a delay in strategy calculation start time lags behind the tick arrival time by more than 27429 ms. Auto trading will be was stopped.
<br>Recommendation:
Reduce the load on the CPU.
<br>
[[File:FS06.png|400px500px]]
<br>
===Main process is not responding during xxxx ms — FS07===
Message: High CPU load. The main MultiCharts window is not responding.
<br>
Possible reasons:
# Add more resources to your machine.
<br>
[[File:FS07.png|400px500px]]<br> ===Study storage operation failure — FS08===
<br>
[[File:FS08.png|400px500px]]
<br>
