Fail-Watch and Trading System Warnings
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.
- 1 Trading System Alerts
- 2 Fail-Watch Alerts
- 2.1 Long delay of the order display in the Order and Position Tracker (the delay exceeds xxxx ms) — FS01
- 2.2 Order display failure in the Order and Position Tracker (the delay exceeds xxxx ms) — FS02
- 2.3 Heavy load on the order processing channel: processing is taking more than xxx ms — FS03
- 2.4 Order processing channel failure: processing is taking more than xxx ms — FS04
- 2.5 Long delay in the calculation of studies (the delay exceeds xxxx ms) — FS05
- 2.6 Study calculation overload: the load has exceeded the computer’s capability (the delay exceeds xxxx ms) — FS06
- 2.7 Main process is not responding during xxxx ms — FS07
- 2.8 Emergency shut down of StudyServer — FS08
- 3 Changing the timeout or disabling the alerts
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.
Message: The broker API is unable to process your orders in a timely manner! Place/modify fewer orders and check your Internet connection.
Order or OCO group placement is taking more than xxxx ms — TR02
Message: The placed OCO group timeout exceeded Broker Order IDs: 1, 2 pending for 2017 ms. It can be caused by an unstable connection to the broker’s servers. As a result, closing position and processing the orders can be delayed.
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.
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.
Long delay of the order display in the Order and Position Tracker (the delay exceeds xxxx ms) — FS01
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.
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.
Heavy load on the order processing channel: processing is taking more than xxx ms — FS03
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.
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.
Order processing channel failure: processing is taking more than xxx ms — FS04
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.
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.
Long delay in the calculation of studies (the delay exceeds xxxx ms) — FS05
Message: <Strategy name> (<instrument name>) strategy calculation start time lags behind the tick arrival time by xxx ms.
This message is displayed if a strategy calculation time lags behind the arrival time of a tick which initiated the calculation.
Study calculation overload: the load has exceeded the computer’s capability (the delay exceeds xxxx ms) — FS06
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.
Recommendation: Reduce the load on the CPU.
Main process is not responding during xxxx ms — FS07
Message: User Interface of MultiChart64. exe (PID = 19784) process is not responding. Last successful response time is xxx.
- The machine on which MultiCharts is launched is lacking technical resources and the CPU is not capable of processing all MultiCharts commands in time. Therefore, there are delays with the command executions which are recorded by the system.
- Overall system load is approaching its limits because the CPU cannot timely address the requests from all programs which leads to the system delays.
- MultiCharts and its processes consume almost all system resources which leads to delayed execution of internal MultiCharts commands.
- Antivirus is scanning the system which lowers the overall computer's productivity.
- Any combination of the above-mentioned reasons is found.
- Decrease the number of MultiCharts and Portfolio Trader instances opened at a time; close excessive charts, scanners, and other MultiCharts windows; decrease the data range on your charts, in the Scanner and Portfolio Trader; decrease the number of auto trading charts; make sure you have only 1 Order and Position Tracker opened.
- Exit all other applications/programs while MultiCharts is running to lower the load on the CPU and disc.
- Wait for the antivirus to finish its scanning or disable it completely.
- Add more resources to your machine.
Emergency shut down of StudyServer — FS08
Changing the timeout or disabling the alerts
If you are satisfied with the current performance, do not observe any issues in the operation and consider this alert excessive, you can change the timeout or completely disable the alert in MultiCharts -> File -> Preferences -> Trading tab -> Fail-Watch and trading system warnings.