Page 1 of 1

A failure post template that actually helps others

Posted: Tue Oct 20, 2026 3:57 pm
by FXS London Scalper
Posts about losing trades or failed strategies can be very helpful, but often lack the details others need to learn from them.

A template:

What I tried: strategy or setup in one paragraph.
Market and timeframe: pair, session, chart timeframe.
Period: dates and number of trades.
Expected: what the backtest or plan suggested.
Actual: what happened.
Costs: spread, commission, slippage assumed vs actual.
What went wrong: best explanation.
What I'd do differently: specific changes.
Chart: screenshot of a typical failure, with time and spread visible.

The most useful part is often "what went wrong", if it's specific. "The market changed" isn't helpful. "The setup relied on Asia range breaks, but over the last two months Asia ranges were narrower than usual and breaks failed more often" is.

Failure posts take courage. Constructive replies help encourage more of them.

Would you use a template like this for posting a failure?

Re: A failure post template that actually helps others

Posted: Sat Oct 31, 2026 10:25 pm
by Shadow Trader
The platform updates itself on a schedule the user doesn't control. A new build arrives overnight, the terminal restarts, and the expert advisor that ran fine for six months now behaves differently.

Changes between builds can affect order functions, how the strategy tester processes data, how time is reported, and which function arguments are accepted. A script that relied on an old quirk stops working, sometimes silently.

The failure mode is nasty. The EA loads, shows a smiley face, and does nothing. Or it trades with a subtle difference, such as a rounded lot size or a changed slippage handling.

Some brokers allow older builds to run for a while. Others force updates as soon as the server version changes.

A routine that helps: after any update, run the EA on a demo or a micro account for a session and compare its behavior with the logs from before. Reading the release notes of the build also helps, though they're often cryptic.

Keeping a copy of a known-good installer is a cheap insurance, as is a note of the build number that worked.

How long did it take to notice that a platform update had changed how a script behaved?