Page 1 of 1

Apex: emotional reset after soft breach warning

Posted: Sat Sep 19, 2026 6:50 pm
by LondonScalper
Apex soft breach warning: emotional reset

A soft breach warning is not primarily a technical problem. It is an emotional one wearing a rulebook. The account is still alive; your nervous system thinks it is already blown and starts hunting for a heroic recovery scalp.

My reset after a warning is deliberately dull:
  • Immediate flatten and platform close for the rest of that calendar day. No “careful” trades while adrenaline is up.
  • Next day: half size, written max clicks, no gold if gold caused the scare.
  • Journal the warning as a process event, not a badge of toughness or a story to tell.
I do not try to “earn the warning back” the same session. That is how soft becomes hard. The goal is to return tomorrow with a smaller ticket and a clear head, not to prove the warning wrong before dinner.

If you have taken a soft breach warning on Apex (or similar), what reset actually kept you from finishing the account off?

Re: Apex: emotional reset after soft breach warning

Posted: Sun Sep 27, 2026 1:48 pm
by PropScalpDesk
Half size the next day makes sense. The part I'd write down as well is when full size comes back, because otherwise that decision gets made by mood too. Some people stay small for weeks out of fear; others jump back to full size after one green morning, which is the recovery hunt again, just a day late.

My rule after a warning: three sessions in a row inside all written limits, regardless of P&L, then back to normal size. A red day within the rules still counts; a green day with a broken rule resets the count.

It's also worth checking afterwards whether the warning came from one trade or from a slow build-up across the day. The fixes are different. One oversized gold ticket needs a sizing rule; five medium losers need a trade-count cap.

Re: Apex: emotional reset after soft breach warning

Posted: Sat Oct 17, 2026 12:16 am
by Shadow Trader
Half size is a sensible default, but I would tie the next day's size to what is left of the drawdown rather than to normal size. After a warning the buffer is often much thinner than it feels, and half of a size built for a full buffer can still be too much.

Say the trailing drawdown is 2,500 on a 50k account and the bad day used 1,600 of it. With 900 left, a normal 250 risk per trade leaves room for barely three stops, and even at half size it is only seven.

My rule is that no single trade may risk more than an eighth of the remaining buffer. Here that is about 110, which comes out a little under half size and grows back on its own as the buffer recovers.

That sits well with PropScalpDesk's three clean sessions. The counter decides when I am allowed back to normal, and the buffer decides whether normal is even possible yet.

On the cause check, my one warning came from slow build-up, six small losers on a choppy morning. The fix was a cap of four trades before 10:00 London, which felt silly until it held me back on two later mornings.

Re: Apex: emotional reset after soft breach warning

Posted: Sun Oct 18, 2026 1:40 am
by Shadow Trader
Something worth checking after a warning is how the trailing drawdown is measured. On the evaluation version I traded, the threshold followed the highest open equity, not the closed balance, so a winner that gave back profit still shrank the buffer.
img_12544_r2.png
img_12544_r2.png (83.05 KiB) Viewed 119 times
The chart is that case in round numbers. With 900 of buffer left, a trade ran to 600 open profit and the threshold rose with it, then I closed at plus 200 and was left with a buffer of 500 after a winning trade.

Under my eighth of the buffer rule, that one winner cut the next trade's risk from about 110 to about 60. It felt like being punished for a good entry, but the arithmetic was right.

So during the reset days I use a fixed target rather than letting runners breathe. Giving back open profit costs real buffer on that kind of account, and half size does not change that.

It also changes how PropScalpDesk's three clean sessions should be read. Three green sessions can still leave the buffer smaller than before if each one peaked well above where it closed, so I check the threshold, not the balance, before going back to full size.