Breakeven That Arms on a Price Cross, Not Just a Fill

If you trigger breakeven from a take-profit level, there is a case where the old behaviour walked straight past a trade it should have protected.

Breakeven waited for a fill. Price had to reach TP1 and one of your orders had to close there before the stop moved. That works whenever you have volume sitting at that level. It does nothing at all when you do not, which happens more often than you would think: your allocation put nothing at TP1, or the earlier layers had already closed there, or redistribution moved your targets and left that level empty.

So price could run cleanly through TP1, stall, and come all the way back to your stop, with breakeven never having armed. The level was reached. Nothing was filled. Nothing moved.

Breakeven now also arms on a price cross. Price trades through the level, holds there for two seconds, and the stop moves, whether or not an order was waiting.

This changes live trades, so it is worth opening your breakeven setting and deciding what you want. If you specifically prefer the old behaviour, where breakeven follows realised volume rather than price, that is a legitimate choice and you should set it deliberately rather than inherit it.

The two-second hold

The hold exists to filter wicks. A single tick through a level on thin liquidity is not price reaching your target, it is noise, and arming breakeven on it would move your stop on the strength of something that did not happen.

Two seconds is short enough that a real move always clears it and long enough that a spike does not. It is not a setting, and I would rather not make it one. A tunable wick filter is a knob people will turn until it stops doing its job.

Breakeven has to actually protect

The other change in this release is that the engine now checks that a breakeven move improves your position before it makes it.

That means two things. A breakeven stop can never land on the losing side of your entry, below it on a buy or above it on a sell. And it can never push a stop that is already protecting you backwards, which is what used to happen when a second breakeven event fired on a trade that had already moved past one.

There is also a guard against the case where the requested stop is on the wrong side of the current market. If a signal asks for breakeven on positions that are underwater, the broker will refuse the modification, and refusing it is correct. What matters is what happens next, and the answer now is that the trade stays as it is rather than being force-closed.

The counter that reports "breakeven applied" counts positions that actually moved, not attempts. It had been counting attempts, which made the number meaningless as a check.

Telegram tells you when it works

You used to hear from the bot only when breakeven failed. Now you get a message when it succeeds too.

Silence is a bad protocol for anything that touches your stop. If the only notification is a failure, you cannot tell the difference between "it worked" and "the notification system is broken", and you end up checking the dashboard anyway.

Cancel behaviour you can choose

Two related settings arrived with this release, both about what happens to your remaining limit orders.

You can now choose whether a limit-order cancel applies only to trades that actually filled something. The old unconditional behaviour was cancelling trades that had never filled anything at all, at a median of about two and a half minutes in, against channel timeouts of thirty minutes or more. That is a setup killed before it had a chance.

And you can cancel remaining limits when a signal triggers a partial close. Of 417 partial-closed trades in one month, 97 still had live limit orders able to re-enter the deeper layers while the trader was winding the position down. If you are taking profit off the table, you probably do not want the trade quietly rebuilding itself underneath you.

Two more

You can pick which topics inside a Telegram forum group TTMT listens to, so a follow-up posted in one topic cannot attach itself to a trade from another.

Dashboard totals now disclose when a disconnected account is included rather than counting it silently. That covered 170 accounts and about $139,000 of profit and loss that nobody could see was in the number.

Start a free 7-day trial at telegramtometatrader.com, or read what breakeven automation is and what it cannot do.