Direct answer
False Breakout is typically defined from inputs that describe (1) what level price is expected to break, (2) what counts as an attempted breakout, (3) what counts as failure after that attempt, and (4) the timeframe and measurement rules used to compare price to those levels.
Because different providers and charting communities may implement the concept with different rule details, the safest way to explain “which inputs it uses” is to list the rule inputs that are required in any implementation, and to separate those stable mechanics from variable choices (timeframe, lookback, and exact thresholds).
Mechanism or definition
A practical way to define False Breakout is as: price moves beyond a reference level (a breakout attempt), but then does not sustain above/below that level according to the rules. The inputs therefore fall into two groups: level inputs and decision rules.
1) Reference-level inputs
These inputs specify the level that the market “breaks.” Common reference types include:
- Prior swing high or swing low.
- Range boundaries (support/resistance created by prior highs/lows).
- A moving average or other baseline used as a dynamic boundary (only if the method explicitly defines it as such).
2) Breakout-attempt inputs
These inputs specify how you detect that a “break” happened. Typical measurement choices include:
- The timeframe used for evaluation (for example, using candle closes rather than intrabar ticks).
- The rule for crossing the level (for example, whether a single wick/touch is enough or whether the close must be beyond the level).
- Whether you require the level to be exceeded by a fixed buffer (a small margin) or whether any crossing counts.
3) Failure-condition inputs
These inputs specify when the attempt is considered a failure. Typical failure inputs include:
- A return back through the level within a defined number of bars.
- A closing condition (for example, the candle close back on the opposite side).
- A “sustainability” condition that demands multiple closes (some methods require more than one confirming bar).
4) Dependency inputs
Some inputs affect results without changing the definition:
- Lookback window for identifying the reference level (how far back you search for the swing or range boundary).
- Evaluation window (how long you allow the failure condition to occur after the attempt).
- Treatment of edge cases: do you allow multiple attempts inside the same structure, and how do you de-duplicate overlapping detections?
Evidence or example
Without assuming any live prices or a specific provider’s proprietary implementation, you can still demonstrate the inputs with a rule-comparison example.
Example of a complete input set (illustrative, rule-based):
- Reference level: the most recent swing high on the chosen timeframe.
- Breakout attempt rule: the next candle closes above that swing high.
- Failure condition: within the next N candles, price closes back below the swing high.
- Parameters: timeframe = T, swing lookback = L, failure window = N.
To independently verify an implementation, use the same input definitions consistently, then count detections where the failure condition is met. The key is that “which inputs” are not just labels; they are the exact measurable conditions (close vs touch, N bars, and how the level is chosen).
Limitations and risks
Material limitations and failure modes include:
- Ambiguous reference levels: different lookback choices can produce different swing highs/lows, changing detections.
- Measurement sensitivity: candle close rules versus intrabar extremes can materially alter which break attempts qualify.
- Overlap and double counting: one move can satisfy multiple attempts depending on how the algorithm handles repeating crossings.
- Market regime dependence: false-break behavior may vary with volatility, trend strength, and liquidity; historical relationships do not guarantee future results.
Also, execution costs and spreads can affect real-world outcomes even if the pattern identification is “correct” on a chart, so the verification should distinguish detection rules from trading outcomes.
Verification or next question
To verify “which inputs” a False Breakout approach uses, compare four items from the implementation you are evaluating:
- How the reference level is defined (fixed vs dynamic, and what lookback is used).
- What exactly triggers an “attempted breakout” (touch vs close; buffer or no buffer).
- What exactly triggers “failure” (return condition and the allowed time window).
- How overlapping signals are handled.