Fail-Watch and Trading System Warnings: Difference between revisions
From MultiCharts
Fail-Watch and Trading System Warnings (view source)
Revision as of 12:38, 22 December 2021
, 22 December 2021no edit summary
mNo edit summary |
No edit summary |
||
Line 5: | Line 5: | ||
The status of the order is being processed in the Trading Server longer than xxxx ms. | The status of the order is being processed in the Trading Server longer than xxxx ms. | ||
<br> | <br> | ||
Message: The | Message: The order status is delayed. Place/modify fewer orders and check your Internet connection. | ||
<br> | <br> | ||
[[File:TR01.png| | [[File:TR01.png|500px]] | ||
<br> | <br> | ||
===Order or OCO group placement is taking more than xxxx ms — TR02=== | ===Order or OCO group placement is taking more than xxxx ms — TR02=== | ||
Message: | Message: OCO group placement is delayed. Place/modify fewer orders and check your Internet connection. | ||
<br> | <br> | ||
[[File:TR02.png| | [[File:TR02.png|500px]] | ||
<br> | <br> | ||
===Order modification or cancellation is taking more than xxxx ms — TR03 === | ===Order modification or cancellation is taking more than xxxx ms — TR03 === | ||
Message: | Message: Order cancellation/modification is delayed. Cancel/modify fewer orders and check your Internet connection. | ||
<br> | <br> | ||
[[File:TR03.png| | [[File:TR03.png|500px]] | ||
<br> | <br> | ||
Line 28: | Line 29: | ||
===Long delay of the order display in the Order and Position Tracker (the delay exceeds xxxx ms) — FS01=== | ===Long delay of the order display in the Order and Position Tracker (the delay exceeds xxxx ms) — FS01=== | ||
Message: The | 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> | <br> | ||
[[File:FS01.png|500px]] | [[File:FS01.png|500px]] | ||
Line 36: | Line 38: | ||
===Order display failure in the Order and Position Tracker (the delay exceeds xxxx ms) — FS02=== | ===Order display failure in the Order and Position Tracker (the delay exceeds xxxx ms) — FS02=== | ||
Message: | Message: High CPU load. No data is received on charts or in Order and Position Tracker. Please stop auto trading and restart MultiCharts. | ||
<br>Possible reasons and recommendations: | |||
<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. | # 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. | # 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. | ||
Line 44: | Line 48: | ||
<br> | <br> | ||
=== | ===High load on order sending channel: 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>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> | <br> | ||
Line 52: | Line 57: | ||
<br> | <br> | ||
===Order | ===Order sending failure: 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>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>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> | <br> | ||
Line 64: | Line 70: | ||
===Long delay in the calculation of studies (the delay exceeds xxxx ms) — FS05=== | ===Long delay in the calculation of studies (the delay exceeds xxxx ms) — FS05=== | ||
<br>Message: | <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>This message is displayed if a strategy calculation time lags behind the arrival time of a tick which initiated the calculation. | ||
<br> | <br> | ||
[[File:FS05.png| | [[File:FS05.png|500px]] | ||
<br> | <br> | ||
Line 73: | Line 80: | ||
===Study calculation overload: the load has exceeded the computer’s capability (the delay exceeds xxxx ms) — FS06=== | ===Study calculation overload: the load has exceeded the computer’s capability (the delay exceeds xxxx ms) — FS06=== | ||
<br>Message: | <br>Message: There was a delay in strategy calculation. Auto trading was stopped. | ||
<br>Recommendation: | <br>Recommendation: | ||
Reduce the load on the CPU. | Reduce the load on the CPU. | ||
<br> | <br> | ||
[[File:FS06.png| | [[File:FS06.png|500px]] | ||
<br> | <br> | ||
Line 83: | Line 90: | ||
Message: | Message: High CPU load. The main MultiCharts window is not responding. | ||
<br> | <br> | ||
Possible reasons: | Possible reasons: | ||
Line 98: | Line 106: | ||
# Add more resources to your machine. | # Add more resources to your machine. | ||
<br> | <br> | ||
[[File:FS07.png| | [[File:FS07.png|500px]] | ||
<br> | <br> | ||
=== | ===study storage operation failure — FS08=== | ||
Message: | Message: Study storage operation failure. Please reboot your machine. | ||
<br> | <br> | ||
[[File:FS08.png| | [[File:FS08.png|500px]] | ||
<br> | <br> | ||