In a hypothetical EUR/USD buy, you request Ask 1.0850 and receive a new offer of 1.0853 instead of a fill. In the manual MetaTrader 5 Instant Execution window you can accept or reject that offer. A requote is a response proposing new prices; it does not itself confirm that a position opened or closed. Check the operation history before sending another request.

What a requote actually is

In MetaTrader 5 Instant Execution, the platform sends the offered price with the request. If the broker does not accept it, the server can return a requote with new prices. Price changes during processing can matter, but the response alone does not prove its complete cause. The initial instruction has not filled; a requote is not a placed pending order waiting indefinitely for the market.

In the manual MT5 window, acceptance is a separate decision. MetaQuotes says the new prices are valid only for a few seconds; this describes that interface, not a universal countdown on every platform. MQL5 distinguishes return code 10004 (requote), 10006 (request rejected) and 10021 (no quotes to process the request). Record the actual response: a requote is distinct from a generic rejection or connection error.

A rejected close leaves the position open

A requote can concern an exit as well as an entry. Rejecting a new price does not remove the position’s risk.

Scroll sideways to see the full diagram

A rejected close leaves the position openHypothetical attempt to close a 20,000 EUR long using Instant Execution. The new offer is rejected and nothing executes. Bid falling from 1.20000 to 1.19950 changes floating valuation by −10 USD.CLOSE A 20,000 EUR LONG1 • Before the attemptBid 1.20000 • position 20,000 EUR2 • RequoteNew Bid offer 1.199703 • You reject the new offerNo execution • still 20,000 EUR4 • Later quoteBid 1.19950 • valuation change −10 USD

Hypothetical linear EUR/USD instrument valued in USD. No execution, other actions, SL/TP, fees or conversion in this interval. −10 USD is the change in unrealised P/L from the first to last Bid; neither a requote fee nor a closed-trade result. MetaQuotes describes accepting or rejecting a new Instant Execution offer.

Hypothetical attempt to close a 20,000 EUR long using Instant Execution. The new offer is rejected and nothing executes. Bid falling from 1.20000 to 1.19950 changes floating valuation by −10 USD.

After the message: check current position volume and executed-deal history. Rejection leaves 20,000 EUR unchanged in this model, and 20,000 × (1.19950 − 1.20000) = −10 USD. A response to a request does not replace confirmation of closing.

A requote and slippage are not the same thing

A requote and slippage describe different events. A requote offers a new price for acceptance; slippage measures the difference between an expected price and an actual fill. The slippage glossary entry gives further examples. Under market execution, the trader accepts in advance the price determined under the contract, without a separate price-confirmation step. This does not guarantee execution, immediacy or the full requested volume. A successful fill can differ favourably or adversely from the expectation.

Rejecting a requote leaves that request unexecuted. For a proposed new entry, this means no position was created by the request; for a proposed close, an existing position can remain open, as the diagram shows. Compare current positions and actual deals rather than treating every rejected offer as “remaining out of the market”. A later request may receive different prices, and submitting it still does not guarantee a complete fill.

Where and when a requote shows up

In instant execution, the platform submits the offered price for acceptance and the server can return a requote. This does not establish a fixed spread. Check the execution mode for the symbol independently of ECN, STP or market-maker labels. Market execution has no separate price-confirmation step, so a successful fill can have slippage without a requote; rejection or partial execution is also possible under the applicable rules. Read the order type, filling policy and execution mode together.

Fast quote changes can make the requested price unavailable during processing. News, reopening and thin conditions are relevant contexts to record, but they do not establish a universal requote frequency. Compare the requested price, response, symbol mode and order execution time for similar operations. A long response time alone does not prove that a broker deliberately withheld a fill.

What it looks like in a concrete example

Take an entirely hypothetical Instant Execution request. Anna wants to buy one EUR/USD lot, assumed here to represent 100,000 EUR. The requested Ask is 1.0850, but the server offers 1.0853 before anything fills. With a pip of 0.0001, the offer is three pips worse for this buy. If the full order subsequently fills at that price, its entry-price difference is 100,000 × 0.0003 = USD 30 before fees. Rejecting the offer does not book that USD 30 as a realised loss. No employment-data surprise or particular response time is assumed.

For comparison, assume the same full 100,000 EUR buy is accepted under Market Execution and fills at 1.0853 against reference Ask 1.0850. That executed difference is adverse slippage of three pips, or USD 30 before other costs. The mode itself promises neither that price nor a full fill. Both accepted scenarios share the assumed entry price; an unaccepted requote has no equivalent completed trade.

What to do tomorrow

  1. Check the symbol’s execution mode. Instant Execution can return a requote; Market Execution sets the execution price without another price-confirmation step. A successful market-execution fill may match or differ from the reference, and rejection or partial execution is possible under the applicable rules. Account labels alone do not determine this result.
  2. Check how price deviation works in the symbol’s execution mode. Where the platform supports and honours a deviation field, set it from your plan. On a five-digit quote with a pip size of 0.0001, an illustrative 2–3 pips equals 20–30 points. This is not a universal slippage cap for market execution. Check the server response.
  3. Check event times against the actual quote and execution conditions. A scheduled release is a reason to examine spread, available volume and the plan’s price tolerance. Waiting a fixed number of minutes does not guarantee that liquidity or execution has returned to a particular state. If the assumptions no longer hold, reassess the request before sending it.
  4. Keep a complete response log. Record time and time zone, side, requested size, requested Bid or Ask, server response and actual fills, including improvements and unfilled requests. Compare similar operations with the provider’s execution policy. A later profitable or losing move does not establish whether the earlier requote was justified.