Signalator Watchdog extends Notify Health from awareness to controlled local recovery. It monitors selected Windows applications and trading terminals, detects when they close, stop responding, or need a controlled preventive restart before accumulated memory and resource usage turns into a hang.
Notify Health tells you when a Windows machine or terminal stops reporting. Watchdog adds controlled local restart rules for selected Windows applications and trading terminals, including scheduled preventive restarts for long-running platforms that accumulate memory, handles, and load over time.
Watchdog should not be limited to MetaTrader only. The Windows app can monitor ordinary applications and also provide a dedicated terminal profile for MT4, MT5, and later cTrader.
Monitor selected Windows applications used in your operational workflow. Add apps from a detected running list or choose an executable manually when needed.
Monitor trading-terminal profiles separately from generic Windows applications, with room for trading-aware safety rules as the product matures.
Watchdog rules are configured inside the Windows app. You can detect terminals, add profiles, enable restart rules, run manual restart actions, refresh local status, and review what happened without treating the browser dashboard as the only recovery surface.
Long-running trading platforms are not always meant to run untouched forever. More charts, more EAs, more indicators, and more uptime can gradually increase memory use, handles, CPU pressure, and general instability. A planned restart is often cleaner than waiting for MT4 or MT5 to freeze at the worst moment.
Normal platform operation can accumulate memory and internal state, especially when terminals run for days with multiple charts, indicators, and EAs.
The more automation loaded into one terminal, the more important it becomes to treat restarts as controlled maintenance rather than emergency repair.
Many active MT5 setups benefit from scheduled restarts before accumulated load becomes a visible freeze, delay, or non-responding window.
With three, five, or more platforms on one or several VPS machines, manual restarts become a repetitive operational chore that Watchdog can structure and log.
Watchdog fills the gap between passive monitoring, preventive maintenance, and manual remote-desktop checking. It focuses on local Windows-observable conditions that can be detected and acted on safely.
Windows may still run, but MT4, MT5, a bridge tool, or another operational application may be closed.
The process can exist while the window is not responding. Hung detection helps distinguish “running” from usable.
Opening multiple VPS sessions just to confirm apps are alive wastes time and still leaves blind intervals.
Health alerts reduce discovery time. Watchdog can reduce recovery time when restart rules are appropriate.
A terminal may still be running, but long uptime and heavy EA usage can gradually create enough resource pressure that a planned restart becomes operationally necessary.
For active MT5 environments, regular controlled restarts can be a practical stability measure, especially when several terminals must be maintained at once.
The goal is not aggressive automation. The goal is a rule-based local recovery layer with explicit configuration, cooldowns, limits, and logs.
Select applications from the current running process list instead of forcing every user to browse manually for executable paths.
Relaunch a selected application or terminal when it exits unexpectedly and the rule is enabled for that profile.
Detect hung application windows where the process still exists but the app no longer responds normally.
Restart selected applications or terminals during a defined maintenance window to clear accumulated process state before instability turns into a hang.
Reduce dangerous restart loops with cooldowns, max attempts, and disabled-by-default restart rules.
Keep a clear record of what Watchdog detected, what it attempted, and whether recovery succeeded or was skipped.
Use Detect running apps, Detect terminals, or manual executable selection to create a monitored profile.
Choose restart-if-closed, non-responding detection, or preventive scheduled restart rules only where they make operational sense.
The local Windows app observes closed processes, hung windows, or scheduled maintenance windows.
Watchdog restarts the app when allowed, skips when blocked by limits, and records the result for review.
A Watchdog page should be credible. It should clearly say what local software can recover and where external infrastructure or terminal-side trading state is required.
The Windows app should receive capabilities from Notify, cache the latest known entitlement locally, and degrade safely if entitlement sync is unavailable.
Small Windows setups that need machine monitoring plus restart-if-closed for a limited number of watched apps.
More resources, preventive scheduled restart, non-responding detection, and broader app coverage for active trading operations.
Higher watched-app limits and the full recovery rule set for more complex Windows and terminal environments.
Start with Health if you only need awareness. Add Watchdog when you also want selected Windows applications and trading terminals to be restarted under defined local rules, including preventive maintenance before resource buildup becomes downtime.
