Category: Strategy Behavior | Last Updated: April 2026

Vector strategies manage trades differently on the way out just as they do on the way in. If you've ever wondered why a trade closed at a specific price — breakeven, a partial profit, a full stop — or why running the same strategy across multiple accounts produced different outcomes for what felt like the same trade, this article is the primer on how our exit mechanisms work and why divergence across accounts is a normal part of the picture.

The Exit Mechanisms Used Across the Vector Lineup

Just as different Vector strategies use different entry logic (breakouts, pullbacks, time-of-day setups, etc.), they also use different exit logic. Below are the mechanisms you'll see across our lineup. Not every strategy uses every one, and the specific parameters (distances, triggers, timing) vary per strategy.

• Fixed Stop-Loss — A set price below (for longs) or above (for shorts) the entry. If the market hits it, the position closes at a predetermined loss.
• Fixed Take-Profit (TP) — A set price at which the strategy closes a winning position. Some strategies use multiple TP levels (TP1, TP2, etc.), closing portions of the position at each.
• Normal Trailing Stop — Adjusts the stop-loss continuously upward as the price moves in your favor. Explained in detail in the Trailer Modes in GFB 2.1C article for strategies that offer this mode.
• Step Trailing Stop — Adjusts the stop-loss in discrete increments (staircase pattern) rather than continuously. Also in the Trailer Modes article.
• Breakeven (BE) Mechanism — Once a trade moves a specified amount into profit, the stop-loss is moved to the entry price (or slightly above). From that point on, the worst-case outcome on that trade is zero P&L — which is what a breakeven exit looks like if the trade reverses.
• End-of-Day (EOD) / Time-Based Exit — Some strategies close positions at the end of the session regardless of whether a TP or SL was hit — preventing overnight exposure. The result can be a profit, loss, or breakeven depending on where price closes.

Why the variety? Different entry logic naturally calls for different exit logic. A trend-following setup may need wider stops and trailing mechanisms to let winners run; a mean-reversion setup may need tighter stops and quick TPs. Exit rules, stop protection, trailer mechanics, and position management are all designed specifically around what each strategy is trying to capture. That's why there is no single "Vector exit rule" — there are several, each matched to a strategy.

Why Results Can Diverge Across Multiple Accounts

If you run the same Vector strategy across several accounts (prop or cash), it's very common — especially on volatile days — to see different accounts end the same trade with different outcomes. One account may hit TP1, another may exit at breakeven+X, and another may stop out — all from what looks like the same trade.

The reason: each account gets its own fill price when the strategy enters. In fast markets with visible slippage, those entry prices can differ by a few ticks across accounts — and once that small difference exists, the downstream BE/trailer/TP mechanics trigger at slightly different points for each account.

A Real Example: GFPB 2.1

GFPB 2.1 has a trailer mechanism that moves the stop-loss to entry +20 points once price has moved +46 points from the entry (the internal logic is TP1 − 4 points; with default TP1 at 50, that's 46).

On a day where the market runs up roughly 50 points and then pulls back:

• Account A (filled slightly earlier/better) → already crossed the +46 threshold → trailer moved SL to +20 → pullback stops it at BE+20
• Account B (filled a tick or two worse) → never quite hit +46 → trailer didn't move → pullback goes through entry and stops at the original stop-loss
• Account C (favorable fill + stayed green enough) → makes it back to TP1 after the pullback

All three accounts experienced "the same trade" and ended with three different P&L outcomes. This isn't a bug — it's slippage variance interacting with exit mechanics, and it's a normal reality of running automated strategies across multiple accounts in volatile conditions.

What This Means for You

• A breakeven exit is normal. It means the trade moved enough into profit to trigger the BE mechanism, then reversed into that moved stop. The strategy protected the in-profit position from becoming a loser — exactly what BE is designed to do.
• An EOD close is normal. Some strategies close the session no matter what. The P&L at that moment depends purely on where price was at close.
• Different accounts diverging on the same trade is normal. On volatile days with slippage, this is expected and isn't evidence of a problem.

What would not be normal is if you see behavior that doesn't match any of the mechanisms above, or if every account shows the same unexpected outcome for an extended period. That's when a support ticket is warranted — our team can review the strategy-side behavior on your VPS.

Where to Find the Exact Behavior for Your Strategy

Because the specifics of these mechanisms (BE trigger distance, SL offset, trailer type, EOD time, etc.) vary by strategy and across versions, the authoritative reference is the documentation for the specific strategy you're running — not this general overview. For strategies with dedicated articles (like GFB 2.1C's trailer modes), consult that article directly.

If you can't find the exact behavior for your strategy, open a support ticket. Our team can explain the specific exit logic for that version, or point you to the relevant walkthrough if one exists.

Bottom Line

Vector strategies use a mix of fixed SL, fixed TP (sometimes multi-level), trailing, step trailing, breakeven, and EOD exit mechanisms — each matched to the strategy it serves. Breakeven exits and differences across multiple accounts on the same trade are both normal consequences of these mechanics interacting with real market conditions (especially slippage on volatile days). For the exact exit rules of the strategy you're running, consult that strategy's documentation; for anything that doesn't match the mechanisms described here, open a support ticket.