Donaldson R F Trading Infrastructure
Repair a Broken Expert Advisor (MQL5)
An audit and fix of an MQL5 Expert Advisor that freezes, errors, or does not do what it should.
The Problem
Your robot freezes in volatile markets, throws execution errors, ignores its own rules, or was left half finished by a developer who disappeared. You need to know whether it can be saved and, if it can, to have it fixed.
About this problem
Most broken robots fail in familiar ways: loops that never end, indicator handles created on every tick, orders sent without checking the result, or logic that was copied together from several sources and does not hold. Many projects were abandoned halfway by their developer, and I see this often.
The price is for a standard case: one Expert Advisor with source code of normal size and a limited set of faults. A very large or badly structured project is reviewed first, and I tell you before any additional chargeable work.
What's Included
- A full audit of the MQL5 code you send: logic, order handling, error handling, memory use and anything that can freeze the terminal
- Fixes for the bugs, freezing issues and execution errors found
- Where the original is beyond patching, an honest recommendation to rebuild a clean version, with what that involves
- Testing of the fixed version on a demo account
- A short written summary of what was wrong and what was changed
- A 7-day window after delivery with up to 3 corrections for genuine bugs
What's NOT Included
- Adding features or changing the strategy. That is a separate order
- Code you do not have the right to give me, or code that is protected or compiled only (I need the MQL5 source)
- MQL4 code, which is a different language (see the MT4 to MT5 conversion)
- A full rewrite. If the code cannot be repaired I tell you, and a rebuild is quoted separately under the creation service
- Any promise of profit, of a particular return or of a limit on loss. An Expert Advisor carries out your rules exactly; whether the rules make money is down to the strategy and the market.
- Decompiling, copying or reverse engineering anybody else's robot. I write original code from rules you can document, or I work on code you have the right to give me.
How It Works
- You send the MQL5 source and describe the symptoms: what it should do and what it does instead.
- I read the code, reproduce the fault where I can, and write down what is wrong.
- I fix what can be fixed. If the code is beyond patching, I say so before spending your money, and explain why.
- I test the repaired version on a demo account.
- I send you the fixed files and a short summary, with the 7-day window for genuine bugs.
In practice: you buy the service, send over whatever access or details the job needs, I investigate and do the work, and you confirm it's resolved before we call it done.
Frequently Asked Questions
- My developer disappeared halfway. Can you finish it?
- Very often, yes. Send me the code and whatever documentation you have, and I will tell you honestly whether it is worth continuing or better rebuilt from a clean base.
- What kind of faults do you fix?
- Freezing, execution errors, memory problems and logic that does not do what it should.
- Can you fix a robot I only have as an .ex5 file?
- No. I need the MQL5 source code. A compiled file cannot be repaired.
- Will the repair make the robot profitable?
- No. It makes the robot do what its rules say. Whether the rules are good is a separate question that I do not judge.
- What if it cannot be saved?
- I tell you what I found and why. You are not charged for a repair I cannot carry out.
- Can you add a feature while you are in there?
- Not within this service. A new feature is a separate order, so the original job stays clear and the code stays stable.