What your SwingAlerts alert is doing

Collecting enough candles for its indicators to mean anything.

A brand-new alert using a 200-length average genuinely needs 200 candles before it can say anything honest. On daily candles that is most of a year, which is worth knowing before you wonder why it has gone quiet.

“Why has my new alert not done anything?”

Reading the market, and waiting for the setup to appear.

The resting state. Most of your alerts are here most of the time. An alert only says this while it is actually reading the market — when it stops, it says so.

Something it needs has stopped arriving, so it is not reading the market.

A gap in the data, or an indicator that has gone quiet, leaves an alert unable to read the market. It keeps its place and picks up where it left off, but until the candles come back it cannot tell you the setup appeared. Hover the badge to see how long it has been this way: a minute or two is an ordinary hiccup, while days mean an indicator that is never going to get what it needs on that pair.

“Why is this alert not reading the market?”

The setup is true right now and the clock is running.

One candle where it is not true sends the alert back to watching, and the clock starts again from zero. So does a gap in the data longer than two candles — a hold we cannot vouch for is not a hold we will count.

“How close is this to firing?”

It happened, and you have been told.

What comes next is whatever you chose under re-arming: either it goes back to watching once the setup breaks, or it is finished until you wake it up yourself.