Most EA failures are not pure code failures. They come from oversized lots, missing alerts, correlated positions, VPS interruptions or strategy settings that were changed without tracking.
The checklist
- Define maximum daily and account drawdown before launch.
- Set lot size from account risk, not from backtest excitement.
- Track magic number, symbol and EA version.
- Monitor margin level and free margin.
- Use heartbeat alerts for stale terminals.
- Keep a rollback copy of the working EA settings.
Before going live
Forward test the EA on a small or demo account, but do not only watch closed P/L. Watch the equity curve, floating drawdown and behavior around sessions or rollover. If the EA performs well but creates deep floating pain, size it accordingly.
After going live
Review weekly. Compare the current version to prior settings and check whether risk stayed inside the expected envelope. Pair this checklist with How to track EA performance.
Turn the checklist into explicit limits
A risk checklist is useful only when every item can produce a clear pass, warn or block decision. Start with trade-level limits: maximum planned loss, maximum spread, permitted symbols, permitted sessions and whether the stop is present before entry. Then add account-level limits such as open risk, daily loss, total drawdown and margin headroom. Finally add operational limits: stale prices, terminal disconnects, rejected orders and repeated execution errors.
Write the unit and reference point beside every threshold. “Stop at 5%” is incomplete: five percent of starting balance, start-of-day equity, high-water equity or current balance can produce four different boundaries. If the account is governed by an external rule, copy the rule definition into the operating checklist and verify it against the provider’s current terms.
Worked example: a layered decision
Assume a $25,000 account has a $24,300 equity value, $600 of total permitted drawdown room and two open positions with $160 of defined stop risk. A new setup proposes $125 of risk. The trade-level limit of $150 passes, but an account rule that caps combined planned loss at $250 fails because $160 + $125 = $285. The correct outcome is to reduce size or reject the new trade; a green daily P/L number does not override the combined-risk limit.
Include failure modes, not only market loss
- Define what happens when the EA cannot read account state or calculate a stop distance.
- Stop opening new exposure when telemetry is stale; do not treat missing data as zero risk.
- Rate-limit retries after broker rejection so a transient error cannot become an order storm.
- Record the reason for every blocked entry so the limit can be audited later.
- Test restart behavior with existing positions; an EA must reconstruct state rather than assume a clean book.
Review the checklist after a broker change, strategy release or rule change, and after any incident that produced an unexpected position. Pair these controls with strategy-level performance attribution and freshness monitoring. Risk logic built on stale telemetry is not reliable risk logic.
Pre-release verification
Run the checklist in a demo or controlled environment before every material EA release. Verify lot rounding, stop-distance calculation, spread handling and the response to a rejected order. Then restart the terminal with an open position and confirm the EA recovers the position’s identity and planned risk. Test a missing price, an unavailable symbol and a stale account snapshot as deliberate failures.
Keep evidence for each check: EA version, settings hash, account type, terminal build, time and outcome. A checkbox without evidence becomes unreliable after the next change. Assign an owner to every exception and an expiry date to temporary overrides. In production, compare blocked-entry counts and error reasons with the test baseline; a sudden change can expose broker drift or a deployment mistake before it becomes a loss.
Primary source
Technical reference: official MetaTrader documentation. Broker and prop-firm terms can differ; verify the rules for the exact account you operate.
xTriel helps monitor drawdown, margin and heartbeat while your EAs run on MT5.