Skip to content

Guide

Candle-close alerts

A price-touch alert fires the instant a level is tagged. A candle-close alert waits for the bar to finish. That difference decides how many false alarms you get.

What closes actually means

A candle covers a fixed window — one minute, fifteen minutes, four hours. It has an open, a high, a low and a close. A price-touch alert watches the highand low: if price wicks through your level for a single tick, it fires. A candle-close alert watches only the close, and only once the window ends.

Why the distinction matters

Levels get probed constantly. Price pushes through, finds no follow-through, and snaps back inside the range before the bar completes. A touch alert reports every one of those probes. A close alert reports only the ones that held to the end of the bar.

That is a trade-off, not an upgrade. You give up immediacy: on a 4h chart you may learn about a break up to four hours after price first crossed. If you need the tick, use a touch alert. If you need the signal, wait for the close.

Choosing a timeframe

The timeframe sets both the resolution and the delay. A 1m alert can fire within about a minute of the level breaking. A 1d alert fires once per day, at 00:00 UTC. All timeframes here are aligned to UTC, so a 4h candle always closes at 00:00, 04:00, 08:00 and so on.

Cooldown is measured in candle time

A recurring alert is level-triggered: while the condition stays true, it fires on every close. Cooldown suppresses repeats, and it is measured against the candle's own close time rather than the wall clock — so a replayed or delayed evaluation produces exactly the same result as a live one. A cooldown shorter than the timeframe does nothing.

If you want edge-triggered behaviour instead — fire on the transition, not on the state — use a crosses above or crosses below operator.