Project specifications
- Market
- XAUUSD / EURUSD
- TF
- M15
- Platform
- MT5
- Client type
- Professional trader
- Delivery window
- 5 weeks
- Stack
- MQL5, a connection-loss simulator, event logs
- Strategy
- Feed-loss detection + defined behaviour
- Modules
- Conservative mode + event logging
- Testing
- Simulated outage in three sessions
Who this was for
Ramin Jafari
- Role
- Automated trader
- City
- Dubai
- Project reference
- TBT-1411-40
The client's idea
Ramin Jafari works XAUUSD / EURUSD on M15; the opening brief was: When the price feed drops the bot should know what to do, not sit there confused.
Initial challenge
When the feed dropped the expert treated a stale candle as fresh and decided on invalid prices.
Solution
Detection of duplicate candles and frozen prices, a conservative mode during long outages, every event logged, and an automatic return to normal.
Why this design
During a long outage, doing nothing is safer than trading on suspect data. It matches how XAUUSD / EURUSD is actually traded and can be tested against the data already available.
Safeguards and risk control
Every first run happens on a demo account, and the pre-live checklist is filled in before the live connection.
Our next-step proposal
The next step is a quarterly settings review and keeping the documentation current with broker changes.
Portfolio
Measured results
These are the figures the test produced — not a promise about future performance.
- 12 s Order round-trip time
- 99.9 % Runtime stability in test
- 11 scenarios Scenario test coverage
- 1 min Recovery after drawdown
Portfolio
How the delivery ran
Every project moves through these five phases, with the window for each agreed in the specification.
-
Discovery and problem framing
CompletedReviewing the client's environment: terminal build, broker and the account it runs on.
Day 1–3
-
Written specification
CompletedWriting the install checklist and fixing the starting parameters on XAUUSD / EURUSD.
Day 4–9
-
Implementation
CompletedPreparing the handover pack: files, set files and the parameter document.
Day 10–21
-
Testing and validation
CompletedA real run on a demo account, log review and watching the first days of behaviour. A deliberate outage was tested separately in the Asian, London and New York sessions.
Day 22–29
-
Handover and support
CompletedHandover of the documentation, a short walkthrough and the support path.
Day 30–33