forex-scalping.com

Counting how many times you moved the stop in each trade

One column I added to my journal is a count of stop modifications per trade. Each time the stop loss moves, for any reason, the count goes up by one. I also note the direction: toward the entry or away from it.

The reason is that stop management is one of the places where discipline breaks down quietly. Moving a stop further away to avoid a loss is the obvious problem. But moving it too early to breakeven, or trailing it too tightly, also changes outcomes. Without a record, it's hard to see how often these things happen.

After a few weeks of data, patterns usually appear. Trades where the stop was moved away from entry tend to end up as larger losses. Trades where the stop was moved to breakeven very early might show many small scratches that would have been winners with the original stop.

The count is simple to record if you use a trade manager that logs changes, since most do. Manually, you note each change as it happens, which also makes you more aware of each decision.

A plan that says the stop moves at most once, to breakeven, after price reaches a certain distance, can be checked directly against this column. Every trade with more than one modification or a move away from entry is a deviation from the plan.

MT4 and MT5 don't keep a modification history in the trade history. They show the final stop only. If you want a record, either use a trade manager that logs changes or add a small script that writes to a file whenever a stop is changed. The Journal tab also logs modifications, so you can recover the count from there if needed, but it's more work. A small script is easy to write in MQL. It can compare the stop value of each open position with the stored value on every tick and write a line to a file whenever it changes.

It's useful to record why each move happened, at least briefly. A move because price hit a planned trailing level is different from a move because you got nervous. A short code like P for planned and E for emotional is enough. Over time, the ratio of P to E moves says more about discipline than almost anything else in the journal. Being honest with the codes is the hard part. It's tempting to label everything as planned. Writing the reason before making the change, not after, makes it easier to be truthful about it.

Comparing trades with zero stop moves to trades with several can show whether your management is helping. If trades left alone with the original stop perform better on average, your management might be costing you. That happens more often than people expect, especially with tight trailing on volatile pairs. The data might suggest a simpler approach. Small samples can mislead here, so it helps to wait for a decent number of trades in each group before drawing conclusions. A few weeks of normal trading usually gives enough to see the direction.

Target moves deserve the same treatment. Moving a target further out because a trade is going well, or closer because you want to lock in a gain, changes the trade's profile as much as moving the stop. A separate count for target changes completes the picture of how much you're adjusting trades after entry. Adding both counts to your weekly review gives a clear measure of how much you interfere with trades once they're running, and whether that interference is improving outcomes or not. If adjustments are helping, keep them. If not, simplifying the management is the obvious next step.

Counting stop changes and their direction is a great idea. One more detail worth logging is the reason for each change, chosen from a short list such as structure, time, news or nerves. After a few weeks, the share of changes made because of nerves is very revealing. Those are usually the ones that hurt results. Changes based on structure or a time rule can be checked against the plan and kept if they help. A short list keeps the logging quick enough to do during the trade.

Some brokers cap how many orders can be sent per second or per minute, and some cap how many modifications can be made to a single trade. Most traders never run into these limits. Scalpers using trailing logic or frequent adjustments sometimes do.

The symptom looks like a random failure: orders rejected with "too many requests," modifications ignored, or an EA that seems to stop responding. Nothing in the chart explains it.

The limit often sits inside the terms of service, buried in a section on "system abuse" or "fair usage." Some brokers apply it quietly. Others escalate: first a warning, then a throttle, then account restrictions.

Anything that modifies stops on every tick is a candidate for trouble. Trailing a stop by a tenth of a pip every time the price twitches creates hundreds of modification requests per minute, and the server notices.

Rate-limiting the modifications from the client side, for example updating the stop only when it has moved at least half a pip, cuts the traffic dramatically without hurting the logic.

A fair estimate of the ceiling can be found by checking the broker's published limits and then reviewing the EA's modification count in the journal. Some terminals log every modification request. Counting them during a busy hour shows whether the numbers approach any plausible limit. Reducing modification frequency by half costs almost nothing in performance and removes the risk.

Has any broker ever contacted someone over order frequency, and what was said?