How to read the last-fired alert feed

The feed is at the bottom of /alerts, under your rule rows, headed LAST-FIRED FEED. It lists up to the 50 most recent alerts for your account, newest first, and each entry is kept for 30 days. It is read when the page loads and does not update on its own, so reload to see anything new. It is a log of alerts, not a live view of your sites. For the current state of a rule, use Preview now on the rule row, or the lamp on the fleet board or in the instrument.

Each row has four parts. First is the time the alert was sent, in UTC, shown as month-day and hours-minutes with a Z. Second is the site name. Third is the first breach window, written in the site's own local time with its length in hours and the peak value, in the display unit you use. If the alert covered more than one window the row adds how many more. The last part is the delivery word. A row never shows a probability. Alerts compare the forecast hour by hour with your limit and do not use ensemble odds. See how alerts work.

sent means the email was handed to the mail service, in green. failed means the send was refused or errored. A failed row does not use up the hours of that window, so the next 30-minute scan tries again and can add another failed row, or a sent one. skipped_no_key means the service was not set up to send, so the alert was logged with no email and those hours are treated as used. Both of the red words mean you did not get an email for that row. A sent row only means it left our side, so check your spam folder if it is not in your inbox.

The FIRED or CLEAR chip is not in the feed. It is on each rule row above it. It reads FIRED if that site's most recent feed entry is less than 36 hours old, and CLEAR otherwise. It describes how recently an alert went out, not whether the wind is over your limit right now. A site can show CLEAR while the forecast is already over the limit, if an alert was sent more than 36 hours ago and later hours were not new. Under the chip, the rule row also states when it last fired and the delivery word.

Only alerts that reached the sending step are logged. If a rule found no breach, found only missing data, had no email box ticked, was on a plan without email alerts, or covered hours that were already alerted within seven days, nothing is added to the feed. So an empty feed does not mean your rules are fine. It may mean none of those conditions has been met. To find out why an expected alert is missing, work through why an alert did not fire.

Two clocks appear in a row. The send time at the start is UTC. The window inside the row is in the site's own time zone, which comes from the site's coordinates. A row stamped 10-04 06:30Z with a window starting at 09:00 site time is normal for a site in Irish summer time, since site time is one hour ahead of UTC. Compare like with like before deciding the alert was late.

An entry is a prompt to look at the forecast for that site, nothing more. Open the site in the instrument from the link in the email, read the hero value, the exceedance fan and the observation line, and make the decision against your own limit and procedure. If a row says failed or skipped_no_key and you still need the information, use Preview now for that rule and read the windows on screen.