Glossary · Last updated: 9 November 2026 · By TradeCopier Editorial Team
MT4 Off Quotes: What the Error Means for Copied Orders
Off quotes is the MT4 server response for ERR_OFF_QUOTES, error code 136. MetaQuotes gives only the wording 'Off quotes'. In practice it means the server could not fill the order at the requested price, so the request was rejected. A rejected follower order has no fill to match the source.
If you searched for mt4 off quotes, you are probably looking at a rejected order in the MetaTrader 4 Journal or in a copier log. This page explains the message, the related conditions worth checking, and what a rejected follower order means for a copied account.
The short version: an off quotes message is a rejection, not a fill. Check the log entry, compare positions, and only then decide what to do next. No single fix works for every broker, so this page does not promise one.
Key takeaways
- Off quotes (MQL4 ERR_OFF_QUOTES, code 136) means the server did not fill the order at the requested price. MetaQuotes gives only the wording.
- The message is a response to one order request. It does not open a position.
- A rejected follower order is not a fill. Source and follower positions can differ until you reconcile them.
- MetaQuotes documents the code but does not list its causes. Broker server state and market conditions decide the outcome.
- Check the activity log, compare positions, and confirm your route's retry behaviour before you resume copying.
What MT4 off quotes means
In MetaTrader 4, off quotes is a trade server response. The MQL4 runtime error reference lists it as ERR_OFF_QUOTES with code 136 and the description "Off quotes" (MQL4 runtime error codes). MetaQuotes gives no further explanation of the name. Read in plain English, it points to the server having no valid quote to fill the order at the requested price, so it refused the request. That reading is ours, not MetaQuotes'.
MT5 uses different constants for the same kind of outcome. The MQL5 trade server return codes include TRADE_RETCODE_PRICE_OFF (10021), described as "There are no quotes to process the request" (MQL5 trade server return codes). Search your logs for the code number as well as the wording.
The error says nothing about your account balance, your strategy or the quality of the source signal. It describes one order request at the moment the server processed it. A later request may succeed, but that later success is a separate order and should be checked as one.
How one rejected follower order moves through the copy
An illustrative flow. The example symbol and lot size are not a broker quote, a prediction or a performance claim.
Conditions to check after an MT4 off quotes rejection
The MetaQuotes references give the meaning of code 136 but do not list its causes. The points below are conditions named in MetaQuotes reference pages for order requests and return codes. They are things to check, not a diagnosis of your account. Broker-specific causes are not covered here; ask your broker.
- A closed market. MQL5 documents a separate code for this case, TRADE_RETCODE_MARKET_CLOSED (10018), so check the symbol's trading hours before you assume a price problem.
- Price slippage. The OrderSend slippage parameter is described as "Maximum price slippage for buy or sell orders" (MQL4 OrderSend). The MQL4 page does not say which error a limit breach returns, so treat this as something to check, not a confirmed cause.
- An out-of-date price. The OrderSend page says market orders use only the latest bid or ask, and that a fully out-of-date requested price generates ERR_REQUOTE (138), a different code from off quotes.
What off quotes means for copied orders
On a copied account, the follower order is the one that receives the rejection. The source order may have filled normally. That gap is the reason to check both sides. A rejected follower order leaves the follower without the position the source holds, until you decide how to handle it.
A copied order passes through several steps before the broker answers: the source trade is detected, a follower order is built from that account's settings, and the broker responds with a code. Off quotes is the broker's answer at the last step, so the cause can sit earlier in the chain. For a copier, the practical question is not only why one request was refused, but whether the follower account now matches the source. Answer that first, using positions and the log.
The activity log can help you find the attempt. TradeCopier activity records can capture the broker response, fill status and error type for each attempt, and the log can be filtered by ticket number, symbol, account, error type and date range (activity log feature). Use it to locate the rejected attempt rather than relying on the terminal Journal alone.
Do not assume an automatic retry. The cloud routing page describes missed signals during connection loss: they may not be replayed, and automatic reconciliation is not assumed. That text covers connection loss, not broker rejections. How TradeCopier handles a rejected order is not stated on this site, so confirm it with support before you rely on any retry. For a related guide on price rules around news, see freeze levels and off quotes during news.
Reconcile before you change anything. Compare source and follower positions and the activity log, then decide whether to accept the difference, close a position manually or ask support. Opening a replacement order by hand can double your exposure if the original fill later appears.
What to check when you see off quotes
- Step 1
Find the log entry
Search the activity log by symbol, account and time. Note the broker response and whether a fill was recorded.
- Step 2
Compare positions
Match the source positions with the follower positions. A follower position that is missing after a rejection is expected until you decide what to do about it.
- Step 3
Check market hours and the symbol
Confirm the symbol was open for trading at the time, and that the follower account settings for that symbol match the source trade.
- Step 4
Review the terminal Journal
If your terminal's Journal records the response, compare its timestamp with the activity log entry.
- Step 5
Ask your broker
If the same message repeats during normal trading hours, send the broker the timestamp, symbol, ticket number and log entry. Only the broker can see its own server state.
Codes you may see in logs
The table gives the documented wording only. Check your platform and build before you match a code in your own logs.
ERR_OFF_QUOTES (136)
- Platform
- MT4 (MQL4)
- Documented wording
- Off quotes
ERR_REQUOTE (138)
- Platform
- MT4 (MQL4)
- Documented wording
- Requote
ERR_TRADE_CONTEXT_BUSY (146)
- Platform
- MT4 (MQL4)
- Documented wording
- Trade context is busy
TRADE_RETCODE_PRICE_OFF (10021)
- Platform
- MT5 (MQL5)
- Documented wording
- There are no quotes to process the request
TRADE_RETCODE_REQUOTE (10004)
- Platform
- MT5 (MQL5)
- Documented wording
- Requote
TRADE_RETCODE_MARKET_CLOSED (10018)
- Platform
- MT5 (MQL5)
- Documented wording
- Market is closed
Risk note
Copy trading carries risk. A copied account can lose money, and a rejected order can leave the follower account in a different position from the source. This page does not promise any profit, any broker response or any particular fix.
Related pages
MT4 trade copier
How TradeCopier is set up for MetaTrader 4 accounts.
Activity logs
Filter attempts by ticket, symbol, account and error type.
Cloud routing
What to check when a connection is unavailable.
Freeze levels and off quotes
A related guide on price rules around news releases.
FAQ
Common questions about setup, plans and support.
Questions about MT4 off quotes
It is the trade server response documented as ERR_OFF_QUOTES, code 136, with the wording "Off quotes". In practice it means the server did not fill the order at the requested price, so the request was rejected.
No. A requote (ERR_REQUOTE, code 138) is a separate response with a different meaning. Check the code in your log rather than the label you see in a chat thread.
Not by itself. The message is a response to one order. Check whether it repeats, whether it affects other follower accounts, and what the activity log shows for each attempt.
The site does not state this. The cloud routing page covers missed signals during connection loss, not broker rejections, and says missed signals may not be replayed. Confirm the behaviour for your setup with support before you rely on any retry.
Not before you compare positions. A manual order can double your exposure if the original fill later appears. Reconcile first, then decide.
The broker controls its server, prices and liquidity. Send the timestamp, symbol, ticket number and log entry to your broker. This page does not promise a fix.
Sources: MetaQuotes MQL4 runtime error codes and OrderSend reference (docs.mql4.com), and MQL5 trade server return codes (mql5.com), all checked 9 November 2026. Product statements come from TradeCopier's own pages.
