SHARKRULE / Learn

Candle close vs intrabar signals: why a condition can disappear

An intrabar signal uses observations while a candle is still forming. A candle-close signal waits for that candle to finish before evaluating the specified condition. The same price path can satisfy the first rule and fail the second. Confirmation describes the data used; it does not establish that a trade will succeed.

SharkRule · Reviewed

Start with the condition, not the chart marker

A candle summarizes a time interval with an opening price, a high, a low and a closing price. During an unfinished candle, the displayed close can be the latest price observed so far. It is not yet the final close. Indicators calculated from those changing values may change too; TradingView documents this behavior in its explanation of repainting.

Write the rule as a full sentence: which market, which price or indicator, which comparison, which candle interval and when to evaluate it. “Price is above 100 during the candle” and “the completed candle closes above 100” ask different questions. For an upward crossing, the previous observation must be at or below the threshold and the new one above it; merely being above a threshold does not establish a new crossing.

Worked example: a signal appears, then the candle closes below the level

All prices and times below are hypothetical, in quote-currency units, with no asset or trade recommendation. Use a five-minute candle covering 10:00:00 up to, but excluding, 10:05:00 UTC. Its final trade is at 10:04:59.900. Assume the final candle update arrives at 10:05:00.200; these example timings are not an exchange latency promise.

Compare rule A, “the current price is strictly greater than 100 at an observed update,” with rule B, “the final close is strictly greater than 100.” The trace lists selected observations, not every market update. True means this one condition is satisfied, not that an order is authorized.

One hypothetical five-minute candle; all times UTC
Observation timePriceCandle stateRule A: current price > 100Rule B: final close > 100
10:00:0099.00OpenFalseNot evaluated yet
10:01:00100.00FormingFalse: equality is not >Not evaluated yet
10:02:00101.00FormingTrueNot evaluated yet
10:03:30100.40FormingTrue again; no new crossing shownNot evaluated yet
10:04:59.90099.50Last trade in the intervalFalseAwait final candle update
10:05:00.20099.50 final closeClosed update receivedNo new live-price observation suppliedFalse

A high above the level is not a close above it

Assume there are no prices outside the example’s extremes: open = 99.00, high = 101.00, low = 99.00, close = 99.50. The move from open to high is (101 − 99) ÷ 99 × 100 ≈ 2.02%; open to close is (99.50 − 99) ÷ 99 × 100 ≈ 0.51%. These are price changes, not trading returns. The candle finishes above its open but below the threshold of 100.

At completion, “high > 100” is true while “close > 100” is false. Waiting for the candle to close does not make those conditions equivalent. Nor does a disappearing chart marker undo an alert already sent or an order already submitted. Preserve the original observation when investigating what happened.

How to tell which candle was actually evaluated

Binance Spot’s official candlestick stream distinguishes the price field c from the closure flag x: x reports whether the candle has closed. Its t and T fields identify the candle’s start and close times, i identifies the interval and E gives the event time. The field name “close” alone is therefore insufficient. These are exchange documentation fields, not a claim about controls exposed in SharkRule.

Match the market, interval and candle boundaries before comparing two readings. A five-minute candle can finish while an enclosing one-hour candle is still forming. Do not treat the shorter candle’s closure as confirmation of the hourly value. Also distinguish the candle’s period from when its completed update reaches the tool: a screen countdown reaching zero does not prove that the tool has received and evaluated fresh final data.

Evaluation timing, alert frequency and execution are separate

TradingView’s frequency documentation distinguishes “once per bar” from “once per bar close.” A frequency limit can prevent repeated notifications during a candle without requiring that its first notification wait for the close. Those are TradingView terms; they do not establish corresponding settings or an alert integration in SharkRule.

An intrabar evaluation can observe a condition earlier and can also observe it reversing. A close-based evaluation uses the completed value but must wait for it. Neither timing choice guarantees a better outcome. If a rule intentionally remembers an earlier crossing until the candle ends, that is another rule: it is not the same as checking whether the closing price is above the level.

A condition becoming true, a rule allowing an action, an exchange accepting an order and a fill are separate events. Even after a confirmed close, fees, slippage, partial fills, non-fills and exchange outages can change the result. Candle confirmation does not reserve the closing price for a later order or remove the risk of loss.

A practical checklist for a signal that seems to have vanished

For the example, a useful note is: “five minutes, UTC, current price > 100 at 10:02:00; candle still open; final close 99.50 received at 10:05:00.200.” It explains the difference without retroactively pretending the earlier observation never occurred.

  1. Record the exact exchange market and the rule version. Compare the same trading pair and data source, not similarly named markets.
  2. Write down the candle interval, timezone and start/end boundaries. If an indicator uses a longer interval, identify that candle separately.
  3. Specify the input and comparison: current price, high, final close or indicator; above, at-or-above or crossing. Include any previous value required for a crossing.
  4. Record whether the candle was still forming, the observation timestamp and when the tool evaluated it. If the status or timing is unavailable, mark it unknown.
  5. Separate evaluation timing from notification limits and any rule that remembers an earlier event. Do not infer these from a chart marker alone.
  6. Compare the recorded condition with the saved budget, permissions and action status. If an order was submitted, inspect its actual status before assuming it was canceled or retrying it.

Common mistakes and what this comparison cannot prove

Do not label every intrabar change a software defect. A value can change as designed while the candle forms. Equally, do not assume every changing historical marker has the same cause: revised data and other calculation choices can matter. Waiting for one candle to close does not solve all forms of repainting.

Do not reconstruct an exact intrabar sequence from one completed OHLC candle. Its high and low show extremes, not the order or timestamps of intermediate observations. The table above supplies that missing trace explicitly; a historical candle alone would not.

This example compares rule meanings, not profitability. It does not select a timeframe, threshold, asset, allocation or trade size. SharkRule is independent automation software, not a financial or investment adviser, and is not affiliated with or endorsed by Binance or TradingView. Real trading can lose money; account and geographic restrictions still apply.

Next step: inspect the timeframe of one saved rule

Open the localized SharkRule simulator walkthrough linked in Sources. Its current RSI example explicitly uses closed one-hour candles. Use the checklist to compare that explanation with the condition and timeframe of a rule available in your dashboard, and review the virtual budget before choosing whether to start a simulation.

The walkthrough supports this specific example, not a claim that every Shark uses candle-close evaluation or that an intrabar/close switch exists. If a rule’s timing is unclear, resolve that before interpreting its signals. A simulation uses virtual funds and does not authorize real orders; any later eligible real-money setup needs its own rule, budget and permissions review and an explicit start.

Frequently asked questions

Does a confirmed candle mean the signal is correct?

It means the specified candle has finished and the condition is evaluated with that completed value. It does not predict the next price, establish profitability or guarantee execution.

If the wick crossed my level, did the candle close above it?

Not necessarily. In the hypothetical trace, the high is 101 and the close is 99.50. A high-above-100 condition is true, but a close-above-100 condition is false. Check the exact price field named in the rule.

Can an alert remain valid even when its chart marker disappears?

An intrabar alert can accurately record a condition that was true at its observation time and false at the final close. That is different from an alert explicitly required to wait for the close. Review its recorded input and timing; a changed marker does not retract a submitted order.

Can a closed-candle rule fill exactly at the close?

The candle’s closing price describes a past observation. An order submitted after evaluation reaches an exchange later and faces available liquidity and execution rules. A matching price may occur, but it is not guaranteed by using closed candles.

Official documentation and references

Prepared with AI assistance from the linked official documentation. Examples are hypothetical; no live account tests or return comparisons were performed.