Skip to main content
This guide covers monitoring a watchlist with a scheduled task, so you get told when something happens instead of checking constantly. The key to a useful monitor is thresholds: it should stay quiet until a name does something worth your attention. The concept behind this is Scheduled Tasks.

​
When to use this

  • You track a set of names and want to be alerted to changes
  • You want signal, not a daily report of nothing happening
  • You want to catch big moves, news, or level breaks without watching the screen

​
Step 1: Define what counts as notable

A monitor is only as good as its trigger. Decide what is worth an alert:
Notice the word “only.” That is what keeps the monitor from becoming noise.

​
Step 2: Set the cadence and channel

A monitor that says “nothing happened” every hour trains you to ignore it. Let silence mean “all clear.”

​
Step 3: Make alerts actionable

An alert should tell you enough to decide whether to act:

​
Step 4: Layer monitors if needed

You can run more than one monitor at different sensitivities:
  • A fast, high-threshold monitor for big intraday moves (Telegram)
  • A slower, end-of-day monitor summarizing everything notable (web app)

​
Example variations

A move-and-news monitor:
A level-break monitor:

​
Common mistakes

  • No threshold. A monitor with no trigger is just a recurring report. Define what is worth an alert.
  • Threshold too low. A 1% trigger fires constantly. Set it where a move actually matters to you.
  • Alerts with no context. “NVDA -6%” is incomplete. Ask for the why and the so-what.