How do email alerts work?

An alert rule is a standing question about one site: will the forecast, within the look-ahead you chose, be at or above (or at or below) your threshold. Each rule row reads like If gust at 10 m ≥ 25 mph in the next 24 h · email on. A scheduled scan runs every 30 minutes, reads the forecast for every saved site that has a rule, and sends an email only when it finds a new breach. Email is the only channel today. The page says web push is coming.

Alerts use the primary forecast at the 10 m model level, hour by hour: gust for a Gust rule, mean speed for a Mean speed rule. They do not use ensemble odds, and they do not use your asset height. When your rule's height is not 10 m, the rule row says that alerts evaluate the 10 m level and that the fleet board shows the height-matched value. The alert scan reads about three days of forecast, so a look-ahead beyond that cannot see further. Because the fleet lamp uses ensemble odds at your height, a WATCH or STOP lamp does not by itself mean an email will follow.

The subject reads Wind alert: site name, rule label and forecast within the look-ahead in hours. The body gives the rule, the look-ahead, each breach window in site local time with its length and the peak value and time, a link that opens the place in the instrument, and an evidence line naming the source and fetch time. Speeds in the email are always in mph, whatever unit you use on screen. It adds a note that values are modelled at 10 m and that the email is a planning aid. An alert is a prompt to look, not a go-ahead. It comes from the alerts address alerts@thewindagent.com, so allow it in your mail filter.

Preview shows WOULD FIRE with the windows found, CLEAR with the hours it checked, or UNKNOWN when hours of data are missing, and a footer saying not sent, not recorded. Preview ignores your email tick, any quiet period, your plan and the repeat rule, so it tells you about the forecast, not about whether an email would go. In the feed each line shows the time in UTC, the site, the first window, how many more windows there were and the delivery word sent, skipped_no_key or failed. The state chip on a rule row says FIRED if it last fired within 36 hours and CLEAR otherwise; it reflects recency, not the live forecast. See how to read the feed.

When an alert is sent, every hour of the windows in it is remembered for seven days. A later scan only counts a window as new if its first hour is not already remembered, so a long spell of high wind that continues into later hours does not send again. A genuinely new window later in the forecast does. A failed delivery is not remembered, so the next scan tries again. A skipped delivery, shown as skipped_no_key, is remembered, which means that alert is used up even though no email left. See why an alert did not fire or fired twice.

Email alerts start on Pro. On Starter the email tick is refused with Email alerts start on Pro., and the scan skips any site whose owner's plan lacks alerts. Where paid plans are enforced, an inactive subscription also stops sends. Missing forecast hours count as UNKNOWN and end any open window, and the email's evidence line reports how many hours had no data. Missing data is never treated as calm, and UNKNOWN on its own never sends an alert. See arm an alert rule.