Day 3 recovered cleanly with just over 0.5% \u2014 and that number is not accidental.<\/p>\n
i try to “aim for 0.5%” not because i want to but because BlueGuardian markets this as an account with no profit target, which sounds great on paper. What they don’t lead with is that their payout structure requires 5 profitable days, and their definition of “profitable” is a minimum of 0.5% gain per day. So while there’s technically no target, you effectively need to make at least 0.5% five times in a row before you see any payout at all. That’s a 2.6% minimum return before the account does anything for you, dressed up as a no-target product.<\/p>\n
So yes, I’m aiming for 0.5% days. Not because I can’t do more, but because overshooting creates unnecessary risk for a target I just need to clear consistently. Day 3 counted, so we’re at Day 2 of 5.<\/p>\n
The bigger story today though was the platform.<\/p>\n
MT5 was running with 5\u201325 second delays on order placement and modification. Not a network issue on my end, the lag was specifically on execution. Since MT5 handles this with a queue rather than dropping commands, I didn’t think much of it and went ahead with 7 TP modifications to manage open positions. In cTrader that’s a two-second operation.<\/p>\n
MT5 silently queued all 7 modifications, did absolutely nothing visible for about two minutes, and then disconnected. Whether the modifications went through, partially went through, or got dropped entirely wasn’t immediately clear, which is exactly the kind of uncertainty you don’t want when you’re actively managing positions.<\/p>\n
This isn’t the first time I’ve seen MT5 behave this way. MT4 had the same queuing behaviour years ago and it’s a big part of why I moved to cTrader as my primary platform. The execution model is just fundamentally different, cTrader rejects or confirms immediately, you always know where you stand. With MT5 you’re essentially trusting a queue you can’t inspect. and if there is omore than 1 thing in said queue the plafrom resets on you on a even longer delay.<\/p>\n
It didn’t blow up the day, but it’s worth logging. If the lag persists it’ll affect how aggressively I manage positions over the remaining 3 days.<\/p>\n
![\"\"](\"https:\/\/swingfish.nullx8.com\/swingfish\/blog\/2026\/06\/bg-day3-512x298.png\")
<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"