The honest cons

This list is longer than the last one, and every item on it has emptied real accounts. Read it slowly. The last one is the one that catches careful people, because it arrives dressed as a reward for all the work.
Five ways automation goes wrong
| The problem | What it looks like in practice |
|---|---|
| Over-fitting to the past | A rule tuned until last year looks perfect. It describes last year beautifully and predicts nothing. Lesson seven takes this apart on its own. |
| Fragility when conditions change | A rule built in a quiet ranging market meets a trending one, or meets a spread that doubles at every release. The behaviour that looked clever becomes expensive. |
| Technical failure | A field entered in points where the author meant pips. A symbol renamed with a broker suffix. A Windows update that restarts the terminal overnight and reattaches nothing. |
| Connection and machine dependence | The terminal must be on and connected for the program to do anything at all, including managing the trades it has already opened. |
| The false comfort of it being handled | The account stops being watched by anybody, because everybody assumes the other party is watching. |
The Lagos version of the connection problem
A program on your laptop stops the moment the power goes, the battery dies or the router drops. The trades it already opened do not close themselves politely. They simply carry on without their manager.
- A stop loss and a take profit sent with the order sit on the broker's server, so they keep working. That is the whole argument for putting them on the ticket at entry.
- Anything the program manages itself, such as a trailing stop, a time based exit or a partial close, stops when the terminal stops.
- New entries do not happen either, so a rule that expects to be flat before the weekend can leave you holding a position into it.
A VPS is a computer in a data centre with power and a connection, rented by the month. It solves the electricity problem and nothing else. A VPS running a wrong setting runs that wrong setting perfectly, around the clock, while you sleep well because you bought a VPS.
Ask the question about any automated setup: if this machine switched off right now, what would be left running on the broker's server, and what would simply stop? If you cannot answer that, you do not yet know what you have built.
The false comfort of it being handled
The other four problems announce themselves eventually. This one does the opposite. Everything appears fine, the terminal is green, trades appear in the history, and weeks pass without anybody actually reading what the program has been doing.

A running program is not a supervised one. The account is still yours and the money is still yours, and on the day it does something strange it will do it at full speed while you are certain that it is handled. Check it on a schedule, not when you happen to remember.
- Nobody has opened the Experts tab in a fortnight to see whether it is still logging.
- Nobody has compared the trades it took against the rules it is supposed to follow.
- Nobody has noticed that the average loss has been drifting wider since the spread changed.
None of this argues against automation. It argues against unattended automation, and against automating a rule nobody has tested. Every item on this page is survivable by a person who expects it and fatal to a person who does not.
The picture to keep
The driver is obedient, not awake to the world. He will not tell you the bridge is out, the fuel is low, or that the route you handed him was drawn for a different city.