On this page
The short version
- A requote means the broker's server refused the price you clicked because the market had already moved — nothing fills until you accept the new price.
- Requotes differ from slippage (filled at a different price) and rejections (request refused outright); MetaTrader reports them with distinct error codes.
- Instant execution turns price risk into fill-failure risk (requotes); market execution turns it into price-uncertainty risk (slippage).
- Regulators have penalized brokers for asymmetric treatment of favorable vs adverse price moves — not for requoting itself.
- Limit orders, sensible deviation settings, liquid sessions and auditing your own fills reduce requote exposure.
A requote is one of the most frustrating messages a forex trader can see: you press Buy, the platform blinks, and instead of a filled position you get an error saying the price has changed and a new quote is being offered. It feels like the broker is dodging your trade. Sometimes that instinct points at a real execution problem — regulators have fined major brokers for exactly that — but most requotes are a mechanical consequence of how price acceptance works, and there are practical ways to make them rare. This article explains what a requote is, how it differs from slippage and a plain rejection, why it happens, and where the line is between normal market behavior and execution practices regulators have penalized.
What a requote actually is
When you send a market order, your trading platform asks the broker's server to accept the price currently shown. A requote means the server refused the price you were quoted because the market had already moved by the time your request arrived, and it came back with a different price instead of filling you at the old one. Your platform then presents that new price and asks whether you still want to trade.
The terminology is documented in MetaTrader's own error tables. MetaTrader 4 defines error 138 as ERR_REQUOTE ("Requote"), alongside related codes such as 135 (ERR_PRICE_CHANGED — the price changed) and 136 (ERR_OFF_QUOTES — "Off quotes", meaning the price is no longer valid). MetaTrader 5 uses the newer trade return codes: TRADE_RETCODE_REQUOTE (10004, "Requote") and TRADE_RETCODE_REJECT (10006, "Request rejected"), while 10008 (PLACED) and 10009 (DONE) mark the order being accepted and completed [1][2].
So a requote is not a filled trade at a slightly different price — that is slippage. A requote means nothing was filled until you accept the new price.
Requote, slippage, or rejection?
These three outcomes get lumped together, but they describe different things:
Slippage is the difference between the price you expected and the price at which the trade actually executed — in finance more broadly, the gap between the expected execution price and the actual one [3]. With slippage, your order was filled, just not exactly where the screen showed.
A requote means your order was not filled at the quoted price. The server rejected that price and offered another. You have to act again.
A rejection (
TRADE_RETCODE_REJECTin MetaTrader 5 [2]) means the request was refused outright — for example because the market was closed, the order size was invalid, or there were too many requests in flight. Related MetaTrader 4 codes include "broker is busy" (137) and "too many requests" (141) [1].
The distinction matters because the remedies differ. Slippage you manage by controlling order size and timing; requotes you manage by changing how you submit the order; rejections usually mean a hard rule was hit (market hours, volume limits, rate limits).
Why requotes happen
Requotes are the visible tip of a latency race. Between the moment you see a price and the moment your order reaches the broker's server, the market can move. If the server's acceptance check finds the price stale, it refuses it. The main drivers:
Fast markets. During major data releases or sharp moves, prices change several times per second. Any acceptance window, however small, will refuse prices during those bursts.
Thin liquidity. In quiet hours — late in a session, or around session rollover — the nearest available price may sit further from the last displayed quote, making a requote more likely for the same request.
Latency. Distance between you and the broker's server, routing, and platform load all add milliseconds. On a slow connection the price you act on is older, and stale prices get requoted more often.
Maximum deviation settings. Many platforms let you set how far you will allow the fill to deviate from your quoted price (in pips). If the market moves beyond that tolerance, the request fails with a requote or an off-quotes error instead of filling [1]. A tight tolerance gives you price control at the cost of more failed fills.
Dealing desk confirmation. With some dealing-desk execution models, orders pass through a confirmation step rather than being filled automatically, which adds a window in which the price can move. This is the environment where requotes were historically most common.
Instant execution vs market execution
Modern platforms offer two main execution modes, and the difference explains most of the requote-versus-slippage experience:
Instant execution: you click a specific price; the server either fills you at (or near) that price or refuses and requotes. You get price certainty, but fills are conditional — fast markets produce requotes.
Market execution: you request an order at market, with no specific price attached. The server fills you at whatever price is available when it processes the request. No requote is possible because there was no quoted price to accept — but the gap between your click and the fill comes back as slippage instead.
In other words, instant execution converts price risk into fill-failure risk (requotes); market execution converts it into price-uncertainty risk (slippage). Neither mode changes what the market did — they change who decides how a price move between click and fill is handled.
When the choice of price treatment was the problem
Requoting itself is not misconduct, but the surrounding territory — how a broker handles prices between your click and your fill — has produced some of the largest retail forex penalties on record, and those cases are worth knowing because they show regulators drawing a line.
In August 2011, the National Futures Association fined FXCM $2 million for "slippage malpractices," with client compensation dating back to June 2008. The same reporting notes NFA had earlier fined Gain Capital $459,000 for a similar pattern connected to a "Virtual Dealing" plug-in and comparable slippage settings [4].
In February 2014, FXCM UK reached a settlement with the UK's FCA over asymmetric slippage — roughly $10 million in restitution plus $6.9 million in fines (a combined ~$16.9 million). According to FXCM's own announcement, the average impact per affected trader was only $3.70 — evidence that small per-trade distortions add up at scale [5].
In February 2017, FXCM agreed to pay a $7 million penalty to settle CFTC charges involving fraudulent misrepresentation to customers and regulators, withdrew its US registration and effectively exited the US retail market [6].
The common thread in the slippage cases is asymmetry: filling customers at worse prices when the market moved against them while keeping the better prices when it moved in their favor, instead of passing through the improvement. Asymmetric slippage can hide inside execution that looks normal, because most traders never audit both sides of their fills. That is why execution quality is best judged across many trades, not from one requote message.
What a requote costs you: an illustrative calculation
(The following numbers are an illustrative example, not broker data or a market observation.)
Suppose you buy one standard lot (100,000 units) of EUR/USD when the platform shows 1.08500. Notional cost at that ask: 100,000 × 1.08500 = $108,500. The server requotes at 1.08615 — 11.5 pips higher. If you accept, you pay 100,000 × 1.08615 = $108,615. The requote itself cost you $115 per standard lot (11.5 pips × $10 per pip) compared with the price you originally clicked — before any spread or commission. In fast markets, repeatedly accepting requotes at the wrong moments is one way small, invisible costs accumulate. The tool-checked arithmetic: 0.00115 × 100,000 = 115 [7].
Note that this example cuts both ways: a requote can also be lower than your original price if the market moved in your favor during the window. The requote mechanism is direction-neutral; how a broker treats favorable versus adverse moves is where the regulatory cases above came from.
What you can control
You cannot stop markets from moving, but you can stop feeding orders into conditions that produce requotes:
Use limit orders where price matters more than immediacy. A limit order names your maximum acceptable price; it either fills at that price or better, or does not fill. No requote decision is needed mid-flight.
Set a sensible maximum deviation for market entries. If your platform exposes the deviation/max-slip setting for instant execution, decide in advance how many pips of drift you will tolerate rather than accepting or rejecting quotes one by one in a fast market.
Trade in liquid hours for liquid pairs. Orders on major pairs during overlapping sessions face the smallest click-to-fill price gaps. The same order in the last hour before a session closes faces the largest.
Read the broker's execution policy. Regulated brokers publish how they handle requotes, slippage and price improvements. What you are looking for is whether price improvements are passed to clients and what happens when a price goes stale — the exact practices regulators have penalized when handled asymmetrically [4][5].
Audit your own fills. Compare your requested prices against executed prices across a sample of your trades, in both directions. This is the only reliable way to detect asymmetric treatment of favorable and adverse moves — the practice behind the FXCM UK settlement [5].
Limits of this explanation
Execution mechanics vary by broker, platform, regulatory regime and account type, and this article describes general patterns rather than any specific provider's behavior. Regulatory actions cited here are historical cases against specific firms; they do not imply that any current broker requotes unfairly or that requotes indicate misconduct. Platform error codes describe how MetaTrader reports these conditions, not how your particular broker configures its server. Before choosing execution settings on a live account, verify them on your broker's own documentation and demo environment.
Sources & further reading
Check the original source for its scope, publication date and latest terms.
- MetaTrader 4 — Trading Errors (ERR_REQUOTE, ERR_OFF_QUOTES)https://docs.mql4.com/trading/errors
- MetaQuotes — Trade Server Return Codes (TRADE_RETCODE_REQUOTE)https://www.mql5.com/en/docs/constants/errorswarnings/enum_trade_return_codes
- Wikipedia — Slippage (finance)https://en.wikipedia.org/wiki/Slippage_(finance)
- Finance Magnates — NFA fines FXCM $2 million for slippage malpractices (Aug 2011)
For education and research, not personal investment advice. Trading involves risk. Broker terms and protections depend on your country, account and contracting legal entity.



