Trendline Break and Retest: Wait for the Close, Plan the Exit

Video: Give Me 33 Minutes and You’ll Never Place a Dumb Trade Again
Creator: Tori Trades
Original Video: Watch the original video
Difficulty: Advanced

The Big Idea

A line-cross alert is a request for attention, not an entry instruction. The source separates a trendline break, a later retest, and a completed candle that still respects the line. Its broader lesson is to prepare the reference and the exit rules before the urgency of a moving market takes over.

The Line Has to Exist Before the Break

The creator starts analysis from the monthly chart and moves down through weekly, daily, and smaller intervals. Her drawing rules seek many touches, connected lines, and no price intersections. The purpose is a coherent map leading toward the chosen trading timeframe, not a line drawn only because the next move makes it look useful.

That process is still partly discretionary. Two people may choose different anchor points or revise a line differently when moving between intervals. Save the line and its availability time before evaluating a break; a later adjustment cannot justify an earlier trade as if the revised line existed then.

The source’s claim that this can reduce impulsive entries is a process hypothesis. Waiting creates more structure, but does not eliminate fakeouts or establish a universal improvement in returns. It can also delay entry or leave a move untraded when no retest occurs.

Three Conditions, Three Availability Times

ConditionWhat must be observedShortcut to avoid
BreakPrice crosses the prepared line under the chosen rule.Treating an alert as a completed entry model.
RetestA later return reaches the line from the other side.Using the breakout candle’s own range as proof of a later retest.
CloseThe selected retest candle completes while still meeting the rule.Using its final shape before the candle has closed.

The source emphasizes that the trader can step away between stages using alerts. The practical benefit is reduced screen-driven urgency. Alert delivery, however, depends on the platform, settings, and data. A notification is not proof an order executed or that the next price remains suitable.

Define what respectful retesting means: an exact touch, a tolerance zone, a wick allowed through, and the required closing side. The presentation uses examples rather than one numerical rule covering every case. The indicator’s tolerance and bullish-close requirement are original definitions.

Freeze a Broken Ray Instead of Redrawing It Into Success

A trendline is a projection from known anchors. Extending that geometry forward is not using future price data, but choosing anchors after observing the future would be. Once a break has occurred, keep the broken reference fixed while evaluating its later return.

The original indicator uses two confirmed declining pivot highs for a long-side breakout proxy. Each pivot requires later bars to confirm, so the ray is not available at the earlier pivot candle. The script waits until the candidate is unchanged across adjacent observations before checking its break.

On a break, the slope and anchor are frozen. The later retest is checked against that same projected ray, not a new line fitted around the return. New pivot information can be recorded for future candidates while the active ray remains unchanged.

A Nearer Line Is a Different Invalidation Hypothesis

In the replay, the source considers a broad opposing line and then a steeper line to reduce the distance at risk. That can create a nearer structural reference, but a smaller plotted loss does not prove the new line is more valid. The closer reference may fail during normal movement.

Select and record the rule for choosing that line before outcomes. If a stop is tightened only because the original position is too large for the account, consider whether size should change instead. Redrawing the structure to achieve a desired dollar risk confuses analysis with sizing.

The contract multiplier changes money risk

These fictional calculations assume a mini-like value of $5 per point and a micro-like value of $0.50 per point. Verify actual contract specifications separately.

StepObservation or calculationMeaning
Price riskEntry 51,000; stop 50,900A one-hundred-point planned distance.
One larger contract100 × $5$500 before costs.
One smaller contract100 × $0.50$50 before costs.
Fixed hypothetical $120 ceilingTwo smaller contracts risk $100; three risk $150Round size to respect the ceiling rather than round exposure upward.

The source’s mini and micro examples use slightly different fills and displayed risks. Their dollar results should not be compared as if every entry and stop were identical. A one-tenth contract-value relationship only produces a one-tenth price-distance result when the compared price path, size, and execution are also held constant.

Two Exit Policies Ask Different Questions

The source offers an exit near relevant support or resistance, or an exit governed by the opposing trendline. The fixed objective can finish earlier. The line-based approach may capture more of a continuing trend but must tolerate some giveback and usually a longer holding period.

Neither should be selected after seeing which made more in the example. Write the policy in advance, including whether a close or an intrabar violation triggers action and how a trailing reference is updated. Then compare matched entries under both policies.

Compare exits using one original risk unit

This fictional long example assumes fill 100 and initial stop 98, with no costs.

StepObservation or calculationMeaning
Initial risk100 − 98 = 2One R is two price units per share-equivalent.
Fixed objectiveExit 104Gross result +2R.
Trailing outcome APrice reaches 107, later exits 103Gross result +1.5R despite a higher interim price.
Trailing outcome BDifferent path exits 110Gross result +5R; this does not establish which policy is generally better.

Separate a Trailing Illustration From a Broker Order

A line moving on a chart does not automatically update a protective order. The source notes that broker capabilities vary and some trailing adjustments must be manual. A stopped connection, delay, gap, or rejected modification can create a different execution path from the drawing.

The later replay also allows some wicks through a line and discusses moving the line to include them. That is an additional discretion rule, not an automatic exception a test can invent after a profitable recovery. Define a tolerance and whether it is known before the potential exit.

Do not label a hypothetical trailing level as a guaranteed worst-case profit. An intended stop can fill differently, and the position still has costs and operational exposure. The code below does not manage an account or imply that it can implement the full trailing method.

Plan for No Retest and for a Failed Retest

The market may break and continue without returning. It may return and close on the wrong side. It may retest long after the proposed opportunity is relevant. Each outcome belongs in the sample, rather than being omitted because the illustrated winner had a clean sequence.

The proxy gives the broken ray forty bars to produce a later response. A completed close more than the frozen tolerance below the ray cancels the long setup. One qualifying retest consumes it, and the same broken candidate is not reused. These are original lifecycle choices.

This disciplined sequencing can make a decision less impulsive, but following it does not make every trade sound. The remaining target room, actual fill, costs, instrument, and risk budget still need evaluation.

Pine Script Indicator

View Pine Script Indicator Code
//@version=6
// Guide: https://candlechasers.com/trendline-break-retest-close/
// Original educational indicator. No orders, fills or performance claims.
indicator("CC Confirmed Pivot-Ray Break Retest", overlay=true)
strength = input.int(3, "Pivot confirmation bars", minval=1, maxval=10)
life = input.int(40, "Break-to-retest maximum bars", minval=2)
nearATR = input.float(0.25, "Retest tolerance / ATR at break", minval=0.01)
a = ta.atr(14)
p = ta.pivothigh(high, strength, strength)
var float h1 = na
var float h2 = na
var int x1 = na
var int x2 = na
var int usedOrigin = na
var bool active = false
var float frozenSlope = na
var float anchorPrice = na
var int anchorBar = na
var int born = na
var float tol = na
bool signal = false
if chart.is_standard and barstate.isconfirmed and not na(p)
    h1 := h2
    x1 := x2
    h2 := p
    x2 := bar_index - strength
slope = not na(x1) and x2 > x1 and h2 < h1 ? (h2 - h1) / (x2 - x1) : na
candidate = not na(slope) ? h2 + slope * (bar_index - x2) : na
candidatePrevious = not na(slope) ? h2 + slope * (bar_index - 1 - x2) : na
sameCandidate = not na(x2[1]) and x2 == x2[1]
if chart.is_standard and barstate.isconfirmed
    bool occupied = active
    if occupied
        float ray = anchorPrice + frozenSlope * (bar_index - anchorBar)
        if bar_index - born > life or close < ray - tol
            active := false
        else if bar_index > born and low <= ray + tol and high >= ray - tol and close > ray and close > open
            signal := true
            active := false
    bool broken = sameCandidate and not na(candidate) and close > candidate and close[1] <= candidatePrevious
    if not occupied and not active and broken and (na(usedOrigin) or x2 != usedOrigin)
        active := true
        frozenSlope := slope
        anchorPrice := h2
        anchorBar := x2
        born := bar_index
        tol := a[1] * nearATR
        usedOrigin := x2
activeRay = active ? anchorPrice + frozenSlope * (bar_index - anchorBar) : na
plot(h2, "Latest confirmed high: context only", color=color.new(color.gray, 75), style=plot.style_stepline)
plot(not active ? candidate : na, "Candidate descending two-pivot ray", color=color.orange, style=plot.style_linebr)
plot(activeRay, "Frozen broken ray: awaiting later retest", color=color.blue, linewidth=2, style=plot.style_linebr)
plotshape(signal, "Later retest holds at completed bullish close", shape.triangleup, location.belowbar, color.aqua, size=size.small)
alertcondition(signal, "Pivot-ray retest", "CC: later completed retest of frozen descending pivot ray. Long-context proxy only; no order.")
var table status = table.new(position.top_right, 1, 2, bgcolor=color.new(color.black, 10))
if barstate.islast
    table.cell(status, 0, 0, not chart.is_standard ? "Use STANDARD candles" : active ? "Broken ray frozen; waiting for retest CLOSE" : na(candidate) ? "Waiting for two confirmed declining pivot highs" : "Candidate ray visible; waiting for break", text_color=color.white, text_size=size.small)
    table.cell(status, 0, 1, "Long-only proxy | no monthly-to-hourly chain or automated trailing stop", text_color=color.white, text_size=size.small)

What This Indicator Shows

The script plots the latest confirmed high as faint context, a candidate descending ray in orange, and a frozen active broken ray in blue. It is a long-only experiment. A triangle records a later bullish retest close within a tolerance of 0.25 ATR frozen at the break. Candidate lines may update as new pivots confirm while idle; active lines do not. The status panel explains missing pivots or the current stage.

What This Indicator Does Not Show

It does not reproduce top-down drawings, every no-intersection rule, short entries, discretionary line steepening, support/resistance targets, or automated trailing orders. Three-bar pivot confirmation, the tolerance, forty-bar expiry, and bullish-close condition are ours. The script does not backdate signals to pivot origins. A newer candidate may become eligible after resolution, but the consumed candidate cannot silently rearm without a new pivot origin.

Setup and Validation

Paste the complete code into TradingView’s Pine Editor, save it, and add it to the chart. Use the chart type, timeframe, and context described above, then inspect the status panel and reference plots before expecting a marker. Use Once Per Bar Close for the supplied alert conditions and recreate alerts after changing code or settings. No alert submits an order.

Validation status: Statically reviewed for completed-bar timing, source-versus-proxy distinctions, future-data use, state behavior, reference replacement and expiry, and visible output. This code has not been compiled or chart-tested in TradingView here. No historical performance or live-execution results are claimed. Use replay to check the described behavior and report any compiler or runtime message exactly.

Practice: Freeze the Drawing and Compare Two Exits

Save one prepared line and its anchors before replaying the break. Record the break, later return, completed retest close, and realistic next executable price. Specify one fixed objective and one independently defined trailing rule for the same entry. Keep failed retests and no-return moves, and record every line revision with its timestamp.

Research and Comparison Lab

These are original proposed experiments, not results established by the source. Change one main feature at a time, retain failures and missing opportunities, and reserve later observations for evaluation rather than repeatedly selecting rules from the same outcomes.

Does the later retest improve the whole opportunity?

Compare a breakout-close proposal with a later retest proposal on the same prepared lines. Keep stop methodology, costs, period, and objective fixed. Record missed returns, entry deterioration, and outcomes per eligible break, not only per triggered trade.

Which exit suits the same entry sample?

Compare a fixed pre-recorded structure objective with a frozen-rule trailing policy. Keep size and original risk constant. Measure realized R, time exposed, giveback, and ambiguous intrabar exits; do not substitute maximum open profit for the realized result.

How sensitive is the line definition?

Ask two reviewers to draw lines before outcomes under the source’s rules, then compare with the two-pivot proxy. Record anchor and timing disagreements. This evaluates a meaningful source-versus-code difference rather than assuming the automated line is authoritative.

Check Your Understanding

Does a line-cross alert mean enter immediately? No. The source still requires the later retest and close.

Can a later redrawn line justify an earlier trade? No. Record when the line actually became available.

Does tightening a line always make a trade safer? No. It changes invalidation as well as price-distance risk.

Is a higher interim profit the trailing exit result? No. Only the realized exit price determines that result.

Does the indicator trail a broker stop? No. It is a reference-and-event map only.

Final Takeaway

The source’s break–retest–close sequence can organize patience, but its value depends on prepared references and explicit risk and exit rules. Freeze what was known, compare entries and exits on matched opportunities, and keep chart geometry separate from actual order management.

Risk Disclosure

This material is educational and is not personalized financial, investment, or trading advice. Trading can cause substantial losses. Source-reported results, hypothetical examples, and probability illustrations do not establish future performance. Calculations depend on their assumptions and omit costs unless stated. Commissions, spread, slippage, gaps, leverage, liquidity, borrowing, financing, and changing market conditions can materially affect outcomes. Indicators do not simulate broker execution or establish profitability. Short exposure can involve losses beyond the initial sale value. Evaluate any approach with appropriate data, realistic costs, and explicit risk limits before considering live use.

This is an independent educational companion and is not affiliated with, sponsored by, endorsed by, or authorized by the source creator, channel, or TradingView.

As an Amazon Associate I earn from qualifying purchases.