Execution quality after a platform update: a before/after sample
Posted: Wed Oct 21, 2026 10:18 am
Platform updates (a new MT5 build, a cTrader version, a broker's server migration) occasionally change execution behaviour. Usually it's fine. Sometimes it isn't, and nobody notices until weeks later.
A simple before/after check:
1. Before the update, note your recent averages: entry slippage, stop slippage, reject rate, order-to-fill time from the Journal. Use the last 50–100 trades.
2. After the update, collect the same metrics for the next 50–100 trades.
3. Compare. Look for meaningful shifts, not small noise.
What might change:
- Order-to-fill time, if the update changed how orders are routed.
- Reject or requote behaviour.
- Slippage tolerance defaults on order tickets.
- Behaviour of EAs, if functions changed.
Also check settings after updates: some reset defaults, such as one-click trading or maximum deviation.
It's a small effort. If something did change, you'll have the numbers to raise it with support.
Has an update ever changed your execution noticeably?
A simple before/after check:
1. Before the update, note your recent averages: entry slippage, stop slippage, reject rate, order-to-fill time from the Journal. Use the last 50–100 trades.
2. After the update, collect the same metrics for the next 50–100 trades.
3. Compare. Look for meaningful shifts, not small noise.
What might change:
- Order-to-fill time, if the update changed how orders are routed.
- Reject or requote behaviour.
- Slippage tolerance defaults on order tickets.
- Behaviour of EAs, if functions changed.
Also check settings after updates: some reset defaults, such as one-click trading or maximum deviation.
It's a small effort. If something did change, you'll have the numbers to raise it with support.
Has an update ever changed your execution noticeably?