Signalator Notify is a monitoring, alerting, and controlled recovery product for Windows machines, selected Windows apps, trade terminal health, trade activity, and price conditions.
Signalator Notify FAQ
Answers for setup, monitoring, recovery, and alerts.
Find concise answers about Notify plans, Get Started flow, Windows Monitor, Watchdog auto-restart, Trade Monitoring, Terminal Health, Price Watch, alert delivery, privacy, and troubleshooting.
Notify FAQ
General
Start here if you want the shortest explanation of what Signalator Notify is, what it covers, and who it is built for.
Signalator Notify monitors Windows machine status, selected Windows app and terminal watchdog profiles, trade terminal health, trade activity, and price conditions. This can include a Windows VPS or local Windows machine, MT4 / MT5 / cTrader-style terminal workflows, trade monitoring, price watch rules, and local Watchdog recovery rules where enabled.
Signalator Notify is for users who need operational visibility into Windows machines, selected apps, trade terminals, trade activity, price conditions, or local recovery actions such as controlled app and terminal restart.
Notify Windows is the simpler Windows machine monitoring and local Watchdog recovery product. Notify Pro adds broader monitoring such as trade terminal health, trade activity, and price conditions.
Signalator Notify supports Windows machines, selected Windows app Watchdog profiles, and trading workflows connected through platforms such as MT4, MT5, cTrader, NinjaTrader, and TradingView-connected paths.
No. Signalator Notify can also be used for Windows machine monitoring and selected Windows app recovery.
Yes. Signalator Notify can be used for Windows machine monitoring and selected Windows app Watchdog profiles. Service-level monitoring depends on the exact setup and sender path used.
Notify FAQ
Plans and pricing
These answers explain how the Notify plan structure is positioned and when each level makes sense.
The current Notify structure includes Notify Windows, Notify Pro, Notify Advanced, and Enterprise, with Watchdog recovery included where the Windows app and enabled plan/module allow it. See the full plan comparison on the Notify pricing page.
Notify Windows is the standalone Windows machine monitoring plan. It is intended for monitoring the status of a Windows-based system and, where enabled, using local Watchdog rules for selected apps. Typical examples include a Windows VPS, a CCTV or security workstation, a trading workstation, or another always-on Windows machine that needs uptime monitoring and controlled app recovery.
Notify Pro is the hosted plan that adds broader monitoring beyond Windows-only coverage, including trade terminal health, trade activity, price conditions, and stronger combined use with Watchdog-style operational recovery. See the full breakdown on the Notify plans compare page.
Notify Advanced is the stronger hosted tier for broader monitoring capacity, more profit rule monitoring, advanced profit rule monitoring, enhanced privacy options, additional supported sources compared with Pro such as NinjaTrader and TradingView, and access to extra delivery channels such as SMS. See the full breakdown on the Notify plans compare page.
Consider Enterprise when you need self-hosted deployment, client-controlled infrastructure, or a more customized setup.
Yes. You can start with a smaller Notify plan and move to a broader one later.
Yes. Notify Windows supports up to 2 active monitored resources, Notify Pro supports up to 5, Notify Advanced supports up to 20, and Enterprise is custom for 50+ resources. An active monitored resource means one Windows Monitor or one Trade Terminal connected to Signalator Notify. See the full plan comparison on the Notify plans compare page.
No. Profit Rules and Price Watch rules are counted separately from monitored-resource limits. Current capacity is: Profit Rules — 10 on Pro, 50 on Advanced, custom on Enterprise; Price Watch rules — 25 on Pro, 100 on Advanced, custom on Enterprise.
Notify FAQ
Setup and onboarding
This section explains how a new user usually gets from the first page visit to the first live monitored source.
Choose the right Notify plan, create the monitored source, apply the token or config, and wait for the first live heartbeat or event. Start here: Notify setup.
Create the source that matches what you want to monitor, then connect the correct sender or utility to that source. Use the normal onboarding flow here: Create a monitored source.
A source connection is the monitored object inside Notify that represents the sender side.
They identify the source connection and attach the sender side to the correct monitored object.
Use the Notify downloads page for setup files and apps, or go to Notify setup if you want the normal onboarding path first.
A simple Windows Monitor setup can be done quickly. Broader terminal and trade monitoring usually takes longer. The next step is here: Notify setup.
No. Notify can also run on a local Windows machine or another Windows host.
Install or open the Signalator Notify Windows app, detect or add the Windows app or trading terminal you want to watch, save it as a Watchdog profile, then enable only the recovery rules you want, such as restart if closed, restart if not responding, or scheduled maintenance restart. See the Watchdog page here: Notify Watchdog.
Notify FAQ
Windows Monitor
Windows Monitor is the machine-level monitoring layer. It is not the same thing as terminal health or Watchdog recovery, and it is not limited to VPS usage.
Windows Monitor is the module used to monitor the operational status and basic resource health of a Windows machine, including online/offline state, CPU usage, RAM usage, and free disk space.
Windows Monitor checks whether the machine is still sending the expected heartbeat and can also track CPU usage, RAM usage, and free disk space, so you can see both machine availability and basic resource health.
No. Windows Monitor is for the machine. Terminal Health is for the trade terminal. Watchdog recovery is a separate local layer for selected apps and terminals that may need restart rules.
Yes. Windows Monitor can run on a Windows VPS, local Windows PC, or another Windows machine.
Windows Monitor sends regular heartbeats on a short cadence.
If the machine stops sending heartbeats and crosses the offline threshold, Notify generates the offline event.
Yes. Notify can generate a recovery event when the heartbeat returns.
Windows Monitor is for operational monitoring. It collects the heartbeat signal and the limited source metadata needed to manage the monitored machine correctly.
Notify FAQ
Trade Monitoring
Trade Monitoring is the event layer. It answers what happened in trading activity, not whether the machine or terminal is alive.
Trade Monitoring is the part of Notify that monitors trade-related events.
Notify can detect trade events such as position opened, position closed, position partially closed, pending order events, and stop-loss / take-profit updates.
Yes.
Yes.
No. Trade Monitoring and Terminal Health are separate capabilities.
Yes. That depends on the plan and deployment model.
Yes. Windows Monitor covers the machine, Terminal Health covers the terminal, and Trade Monitoring covers trade events.
No.
The practical trading-terminal focus is centered on MT4, MT5, and cTrader workflows.
Notify FAQ
Terminal Health
Terminal Health exists so users can monitor the operational state of the terminal itself without confusing it with either machine status or trade-event status.
Terminal Health is the part of Notify that monitors whether a trading terminal is operationally alive and still sending its expected heartbeat.
Trade Monitoring covers trade events. Terminal Health covers terminal operational status.
Windows Monitor is for the Windows machine itself. Terminal Health is for the trading terminal running on that machine, such as MetaTrader 4, MetaTrader 5, or cTrader. This means the Windows machine can still be online while a specific trade terminal has stopped, frozen, or disconnected. Watchdog can then be used as the local recovery layer for selected terminal profiles where restart rules are enabled.
If the terminal heartbeat stops and crosses the threshold, Notify generates the terminal-health event.
Yes.
Yes.
Notify FAQ
Watchdog and recovery
Watchdog is the local recovery layer. It monitors selected Windows apps and trading terminals and can restart them when enabled rules allow it.
Notify Watchdog is the local recovery module inside Signalator Notify Windows. It watches selected Windows applications and trading terminals and can take controlled restart actions when configured rules are triggered.
Windows Monitor tells you whether the machine is alive and reports basic resource health. Watchdog focuses on selected apps or terminals on that machine and can restart them locally when enabled recovery rules allow it.
Watchdog can monitor and restart selected Windows applications. For trading use, Terminal Watchdog profiles are intended for MT4 and MT5 first, with cTrader planned later.
The core local rules include manual restart, restart if closed, restart if not responding or hung, and scheduled maintenance restart. The recovery flow can use graceful close, forced kill after timeout, relaunch, cooldowns, max attempts, and local action history.
No. Watchdog profiles should be added deliberately and restart rules should be enabled deliberately. This avoids unexpected restarts for apps or terminals that should only be monitored.
No. The current Watchdog scope is application and terminal monitoring/restart. It is not intended as a Windows OS reboot tool.
Yes. MT4 and MT5 are the first practical Terminal Watchdog targets. These profiles are still local Windows app profiles, with terminal-specific naming and future room for trading-aware safety checks.
Not as a simple Windows-only rule. A safe rule such as restart only if no open positions requires terminal-side trade state from MT4, MT5, or cTrader. That belongs to advanced/future or tailored Terminal Watchdog logic, not the basic local process check.
See the dedicated Watchdog page here: Notify Watchdog.
Notify FAQ
Price Watch
Price Watch is the symbol and price-condition layer. It is there for target levels, crossings, and event-driven level alerts.
Price Watch is the module that generates alerts when a configured price condition is met.
You create a rule for a symbol and a target condition. Notify evaluates the price state against that rule and generates the hit event when the condition is met.
Yes. Price Watch rule capacity is counted separately from monitored resources: up to 25 on Pro, up to 100 on Advanced, and custom on Enterprise.
Price Watch supports target and crossing-style conditions, including greater-than, lower-than, and crossing logic.
Yes.
Yes.
It is designed for event-driven delivery as soon as the configured condition is detected.
Notify FAQ
Alerts and channels
Notify is not only about detecting events. It is also about sending those events to the right place with the right amount of detail.
Notify supports dashboard alerts, Telegram paths, and mobile push.
Yes.
Yes.
Yes.
Yes.
Yes.
That depends on the configured routing and the available alternative channels.
Notify FAQ
Privacy and deployment
Privacy in Notify is strongly tied to visibility control, retention decisions, and deployment model rather than only to message transport language.
Hosted Notify handles privacy through visibility control, retention decisions, and plan-based deployment positioning.
Pro is the standard hosted tier. Advanced adds stronger hosted privacy positioning. Enterprise is the self-hosted path.
Yes.
Yes.
The client controls the server and database in Enterprise.
Yes, when the correct tier and deployment model are chosen.
Notify FAQ
Troubleshooting
This section helps users narrow problems down to the right operational layer instead of treating every issue as the same kind of outage or recovery failure.
That usually means the expected heartbeat or event flow has stopped long enough to cross the configured threshold.
First confirm the source is alive, then confirm the module is enabled, then confirm the event is being generated, and then confirm the delivery path is active. For Watchdog actions, also check that the profile exists, the restart rule is enabled, and cooldown or max-attempt limits have not blocked the action.
Delays can come from heartbeat thresholds, evaluation cadence, channel behavior, or the path between detection and delivery.
This usually happens when Windows Monitor, Terminal Health, Trade Monitoring, and Watchdog recovery are conceptually mixed.
Check the source object, token or config, sender status, first heartbeat or event arrival, and the enabled module. For Watchdog, also check the selected executable path, profile state, enabled rule, and recent local action history.
If the Windows machine stopped reporting, it is a Windows Monitor issue. If the machine is fine but the terminal stopped reporting, it is a Terminal Health issue. If both are alive but trade events are missing, it is a Trade Monitoring issue. If the app or terminal closed, froze, or needed relaunch, it belongs to Watchdog recovery.
Common reasons include the restart rule not being enabled, the app not matching the saved profile, the executable path being unavailable, the process still being inside a cooldown window, max restart attempts being reached, or the app state not meeting the selected rule condition.
Contact support when the source is correctly configured but still not attaching, or when the event or delivery path remains inconsistent after the core checks are complete. Contact us here: Contact.
Still need help?
Choose the next step that fits the question
Go to setup and downloads if you need to install or attach a source, open Watchdog if your question is about app or terminal recovery, move to pricing if you are choosing the right plan, or contact us when the question is commercial, custom, or deployment-specific.