CORVUX MONITOR PREMIUM — TROUBLESHOOTING

CORVUX MONITOR PREMIUM — TROUBLESHOOTING

Common issues and how to resolve them

1. The Panel Does Not Appear on the Chart

Symptom: After attaching the product, no panel is visible.

Possible causes and solutions:

• The chart is too small. The panel requires a minimum chart width of approximately 400 pixels. Resize the chart window or reduce the number of open charts.

• The product is not attached. Verify in the top-right corner of the chart that the product name is displayed. If not, re-attach it from the Navigator.

• AutoTrading is disabled. Although Corvux Monitor does not trade by default, the Kill Switch requires AutoTrading to be enabled. Click the AutoTrading button in the toolbar to enable it.

• The chart is not a standard chart. The product works on standard candlestick charts. It may not display correctly on non-standard chart types.

2. "No EAs Detected" Message

Symptom: The panel shows "No EAs detected" even though you have EAs running.

Possible causes and solutions:

• Auto-discovery is disabled. Check that InpAutoDiscover is set to true .

• No open positions. If no EA has open positions at the moment, the product cannot detect them by Magic Number. Open positions are required for detection.

• Magic Number filter. If InpMonitoredMagics is set, only those specific Magic Numbers will be monitored. Clear this field to enable auto-discovery.

• History scan disabled. Enable InpScanHistory to detect EAs that have traded recently but have no open positions.

• History period too short. Increase InpHistoryDays from 7 to 30 to scan a longer period.

3. The Panel Is Slow or Laggy

Symptom: The panel updates slowly, or the chart feels sluggish.

Possible causes and solutions:

• Too many EAs monitored. Reduce InpMaxEAsDisplayed from 4 to 2 or 1.

• Static cache disabled. Verify that InpCacheStaticLayer is set to true . This dramatically reduces rendering load.

• High frame rate. The product renders at 10 FPS by default. If you want lower CPU usage, you can reduce InpPulseCycleFrames , but the default value is already optimized.

• Chart has many objects. If the chart has hundreds of indicators or objects, the terminal's rendering may be slowed globally. Move the product to a clean chart.

• Old hardware. The product uses canvas-based rendering, which requires a GPU capable of handling bitmaps. On very old machines, performance may be limited.

4. Panel Position Not Saved

Symptom: After restarting MetaTrader 5, the panel returns to the top-left corner instead of its previous position.

Possible causes and solutions:

• Persistence disabled. Verify that InpPersistState is set to true .

• Global variables cleared. MT5 automatically deletes global variables after 4 weeks of inactivity. If you have not opened the terminal in a long time, the saved position may be lost.

• Chart ID changed. Panel position is saved per chart. If you move the product to a different chart, the position from the new chart will be used.

5. Kill Switch Did Not Trigger

Symptom: An EA was marked as ANOMALY, but the Kill Switch did not close its positions.

Possible causes and solutions:

• Kill Switch disabled. Verify that InpKillSwitchEnabled is set to true .

• Confirmation delay. If InpKillSwitchConfirm is true , the Kill Switch waits InpKillSwitchDelaySec seconds before firing. This is a safety feature to prevent accidental closures.

• State recovered. If the EA's state returned to OK during the delay, the Kill Switch is disarmed.

• AutoTrading disabled. The Kill Switch uses OrderSend , which requires AutoTrading to be enabled.

• Insufficient margin. If closing the position would require more margin than available, the order will be rejected.

• Broker restrictions. Some brokers prevent closing positions via market orders during certain times. Check with your broker.

6. Alerts Not Received

Symptom: No alerts appear when an anomaly is detected.

Possible causes and solutions:

• Alerts disabled. Verify that InpEnableAlert is set to true .

• Cooldown active. Alerts are limited by InpAlertCooldownSec . If an alert was triggered recently, wait for the cooldown to expire.

• Push notifications not configured. For mobile push, go to Tools → Options → Notifications and configure your MetaQuotes ID.

• Sound file missing. Verify that the sound files specified in the inputs exist in MQL5/Files/ . Default filenames are alert2.wav and ok.wav .

• No state change. Alerts are triggered only when the overall state changes. If the state remains ANOMALY, no new alert is generated.

7. HTML Report Not Generated

Symptom: Clicking the Export button does not create an HTML file.

Possible causes and solutions:

• File permissions. Verify that MetaTrader 5 has write access to the MQL5/Files/ folder.

• Filename conflict. If a file with the same name exists, it will be overwritten. This is normal behavior.

• Storage full. Verify that your disk has sufficient free space.

• Sandbox restrictions. On some systems, the MQL5 sandbox may prevent file creation. Check the Journal tab for error messages.

8. Snapshot Not Saved

Symptom: Clicking the Snapshot button does not create a PNG file.

Possible causes and solutions:

• Chart too large. The ChartScreenShot function has size limitations. If the chart is larger than 4000×4000, the snapshot may fail.

• Filename invalid. The product automatically sanitizes the filename, but if the symbol name contains unusual characters, the snapshot may fail.

• Disk full. Verify available disk space.

9. Conflicts Detected Incorrectly

Symptom: The product reports conflicts that do not exist.

Possible causes and solutions:

• Netting vs. Hedging accounts. On netting accounts, two EAs cannot have opposite positions on the same symbol. The conflict detection is designed for hedging accounts.

• Multiple Magic Numbers per EA. If a single EA uses multiple Magic Numbers, it may be detected as multiple EAs. Use InpMonitoredMagics to specify which Magic Numbers to monitor.

• Correlated symbols. The product detects conflicts per symbol, not per correlated pair. If you trade EURUSD and GBPUSD in opposite directions, this is not flagged as a conflict.

10. Health Score Seems Wrong

Symptom: An EA has a health score that does not match your expectations.

Possible causes and solutions:

• Baseline not yet learned. The baseline requires at least 3 sparkline samples to begin. Wait for the product to run for 3–5 minutes before evaluating health scores.

• Training mode active. If InpTrainingMode is true , Z-scores are ignored. Set it to false to enable anomaly detection.

• Thresholds too tight. Adjust InpMaxTradesPerHour , InpMaxDrawdownPct , and InpMaxPositionSizePct to match your EA's normal behavior.

• Baseline contamination. If the EA had an unusual period during the baseline learning phase, the baseline will be skewed. Restart the product to reset the baseline.

11. Terminal Freezes or Crashes

Symptom: MetaTrader 5 becomes unresponsive when the product is attached.

Possible causes and solutions:

• Incompatible build. Verify that your terminal is build 3260 or later.

• Conflicting indicators. Move the product to a clean chart with no other indicators.

• Memory pressure. If many products and indicators are running, the terminal may run out of memory. Close unused charts.

• Canvas conflict. Another product using Canvas may conflict. Only one Canvas-based product should be active per chart.

If the terminal crashes repeatedly, remove the product and contact support with the Journal log.

12. Getting Support

If your issue is not listed here:

1. Check the FAQ for additional common questions.

2. Contact support through the MQL5 Market product page.

3. Include the following information:

   • MT5 build number

   • Product version

   • Screenshot of the issue

   • Journal log entries (Toolbox → Journal)

   • Steps to reproduce the issue

Part of the Corvux Ecosystem

Corvux Monitor Premium works alongside the rest of the Corvux family. Each product is designed to work independently, but together they form a complete workflow for disciplined trading.

• Corvux Monitor Premium — Real-time EA health monitoring and anomaly detection.

• Corvux Radar — Market conditions monitor. Volatility, spread, session, and account risk visibility.

• Corvux Gate — Trade permission engine. Session, spread, and news-based trade filtering.

See all products: https://www.mql5.com/en/users/azrael94/seller

#MetaTrader5 #Troubleshooting #Utility #EAMonitoring #MQL5Market