Self-made faults

Looks like a bug. Is a setting · Nigeria

Some fault reports describe a platform behaving strangely and end with a field somebody filled in. This page lists them in that shape: the sentence people write, the setting behind it, and the record that decides between the two — because the difference is a day of waiting versus a click.

The test is the same every time: does the order history agree with your memory? The history holds the size, the level, the time and the account that were actually used. Memory holds the ones you meant to use. Where they disagree, the fault is a setting.

Quick sort

Twelve reports and what they turn out to be

The sentence written to support, and the field that produced it.
What gets reported	What was set
«The loss was far bigger than the move»	A decimal in the volume box
«My stop did not work»	No stop was attached to the order
«The platform closed my trade»	Free margin ran out
«I opened one position and there are three»	Repeated clicks during a slow fill
«The wrong instrument opened»	A neighbouring symbol in the list
«The account is empty and I never traded that»	A different account was being watched
«It charged me overnight»	The position was held past the changeover
«The spread was enormous»	The order went in during a thin hour
«The exit filled at the wrong price»	A gap across a session break
«My indicator disappeared»	A different chart or timeframe
«The withdrawal is blocked»	An open position is holding the funds
«Login stopped working»	The other of the two passwords

Case 1

The size box, which produces the loudest reports

Trade size is a multiplier, so an error in it is an error of scale rather than of degree. A position ten times larger than intended does not feel like a typing mistake while it is running — it feels like the market behaving abnormally.

How to prove it: open the closed order in the history and read the volume there. Compare it with what your plan said. Then compute what one step of price was worth at that size and check the result against the loss. Recheck a number.

How to prevent it: write the size in the plan before opening the ticket, and read the volume box aloud before confirming. Two seconds, and it removes the largest self-made fault on the list.

Case 2

The exit that was never attached

«My stop did not work» has two versions and they are not related. In the first, a level existed and filled somewhere else — a gap, and the history proves it. In the second, no level was ever attached, and the position simply ran.

How to prove it: the order row shows the stop level as a number or as empty. Empty is the answer, and it is not a defect anywhere.

How to prevent it: attach the level in the same ticket as the order rather than «in a minute». A level added later is a level that depends on you being at the screen, which is exactly the assumption the level exists to remove. Protection that did not protect.

Case 3

The click sent three times

During a thin minute a fill can take longer than a person’s patience. Clicking again does not resend the same order — it sends another one. When the feed settles, three positions appear and the account reports a size nobody chose.

How to prove it: three rows in the history with timestamps seconds apart and the same instrument.

How to prevent it: after a click that does not respond, look at the position list before touching the button again. If «Off quotes» or «Requote» appeared, that is the platform answering, and the answer is to wait. Message decoder.

Case 4

Watching one account and trading another

A Personal Area holds several trading accounts and a demo, and the terminal shows one at a time. A deposit credited to one and a position opened on another produce two complaints at once: money that vanished and a balance that never appeared.

How to prove it: the account number on the order row against the account number on the transaction. They are printed in both places for exactly this reason.

How to prevent it: read the account number, not the account nickname, before every transfer and every order. Wrong account, not a bug.

Trading is risky and may not be suitable for everyone; the settings above change how much can be lost, not whether a loss is possible.

Three habits that turn a setting into a disaster

Fixing a loss with size. Doubling after a losing trade changes nothing about the odds and everything about the consequence. It converts an ordinary mistake into an account-level one.
Trading a screen you have not read. Every refusal on this site is documented in the instrument specification before it happens. Meeting them one at a time on a practice account is free; meeting them all at once is not.
Following a stranger’s instruction. Nobody sending unsolicited trade instructions has any obligation to you, and no setting on the account protects against agreeing with one.

Prove it in the record

Which panel holds the evidence for each case above.

Chart and history

If it is not a setting

The sequence that decides whether a report is worth sending at all.

Open the sequence

Make them cheap

All twelve are reproducible on virtual money in a single evening.

Practice account faults

Make every mistake on this page cost nothing

A practice account accepts the same wrong decimal and produces the same alarming number, with virtual money behind it. The button opens the official exness.com sign-up through a partner link.

Open a free demo at Exness