MQL4 ERR_OFF_QUOTES

MQL4 error 136 off quotes: restore a valid quote

MQL4 error 136 off quotes maps to ERR_OFF_QUOTES: off quotes. The trade server could not provide or accept a current executable quote for the request. Capture GetLastError immediately after the failed call, correct the cause, and retry only when the condition can change.

OffQuotesDiagnostic.mq4.mq4
#property strict
#property script_show_inputs

input double Lots = 0.10;
input int Slippage = 3;

void OnStart()
  {
   if(!IsTradeAllowed())
     {
      Print("Trading is not currently allowed or the trade context is busy.");
      return;
     }

   RefreshRates();
   double price = NormalizeDouble(Ask, Digits);
   ResetLastError();
   int ticket = OrderSend(Symbol(), OP_BUY, Lots, price, Slippage,
                          0, 0, "diagnostic", 0, 0, clrNONE);

   if(ticket >= 0)
     {
      Print("Order opened. Ticket ", ticket);
      return;
     }

   int error_code = GetLastError();
   Print("OrderSend failed. error=", error_code,
         " symbol=", Symbol(), " lots=", DoubleToString(Lots, 2),
         " ask=", DoubleToString(price, Digits));
  }
  • Official meaning: off quotes
  • Read the failed API return value first
  • Capture GetLastError immediately
  • Retry only when the condition can change

What MQL4 error 136 means

The official MQL4 runtime table names error 136 ERR_OFF_QUOTES and defines it as “off quotes.” The trade server could not provide or accept a current executable quote for the request.

The error number is evidence about one failed call, not a diagnosis of the whole EA. Read the API sentinel first, then call GetLastError immediately because that function returns the current _LastError value and resets it.

Check these conditions before editing the strategy

Start with the inputs and external state that existed at the failure point. A later log entry or a successful call can overwrite the useful context.

  • The terminal has no current Bid or Ask for the symbol
  • The connection dropped or the quote stream paused
  • The market is illiquid, closed, or moving too quickly for the request
  • The EA resends indefinitely without refreshing price and connection state

Fix the cause, then choose a retry policy

A bounded retry can be reasonable after RefreshRates and a short delay. Each attempt needs a new price and connection check; never use an infinite retry loop.

Keep the original trading and risk rules intact. A workaround that widens stops, increases volume, changes an account setting, or ignores a failed return value can hide the symptom while changing the system.

CheckAction
The terminal has no current Bid or Ask for the symbolRequire a current quote and refresh rates before building the request.
The connection dropped or the quote stream pausedCheck connection state and stop when the terminal is offline.
The market is illiquid, closed, or moving too quickly for the requestWait for a valid market session and record the symbol and timestamp.
The EA resends indefinitely without refreshing price and connection stateUse a small retry limit with fresh quotes and a delay; fail closed after the limit.

Review the complete example

The script refreshes rates before creating the order and records the Ask used on failure. A production EA should add a small retry budget and stop when the market or connection is unavailable.

The example improves validation and logging. It does not prove the operation will be accepted by a broker or behave safely in live trading.

OffQuotesDiagnostic.mq4.mq4
#property strict
#property script_show_inputs

input double Lots = 0.10;
input int Slippage = 3;

void OnStart()
  {
   if(!IsTradeAllowed())
     {
      Print("Trading is not currently allowed or the trade context is busy.");
      return;
     }

   RefreshRates();
   double price = NormalizeDouble(Ask, Digits);
   ResetLastError();
   int ticket = OrderSend(Symbol(), OP_BUY, Lots, price, Slippage,
                          0, 0, "diagnostic", 0, 0, clrNONE);

   if(ticket >= 0)
     {
      Print("Order opened. Ticket ", ticket);
      return;
     }

   int error_code = GetLastError();
   Print("OrderSend failed. error=", error_code,
         " symbol=", Symbol(), " lots=", DoubleToString(Lots, 2),
         " ask=", DoubleToString(price, Digits));
  }
Where Pineify fits

Move from the rule to editable MQL4 source

Pineify can generate or revise one self-contained .mq4 file with MQL4-specific reference context. Its independent static checker returns MetaEditor diagnostics so you can repair source issues before testing in your own MT4 environment.

Open MQL4 Coding Agent

Static diagnostics do not prove runtime behavior, backtest results, broker compatibility, or live-trading safety.

Pineify MQL4 Coding Agent with MQL4 selected and an editable MetaTrader 4 code artifact

A practical workflow

  1. 1

    Confirm the failed call

    Check the API return value before interpreting an error number from the log.

  2. 2

    Capture the error once

    Call GetLastError immediately and record error 136, symbol, prices, volume, ticket, and terminal state relevant to the operation.

  3. 3

    Correct the triggering condition

    Require a current quote and refresh rates before building the request.

  4. 4

    Retest in the target environment

    Compile the revised source, then test with the same MT4 build, broker, symbol, account permissions, and market state.

Frequently asked questions

What does MQL4 error 136 off quotes mean?

ERR_OFF_QUOTES means off quotes. The code should still identify which API returned failure and log the inputs used for that call.

What usually causes MQL4 error 136?

The terminal has no current Bid or Ask for the symbol The connection dropped or the quote stream paused The market is illiquid, closed, or moving too quickly for the request The EA resends indefinitely without refreshing price and connection state

Should an EA retry after error 136?

A bounded retry can be reasonable after RefreshRates and a short delay. Each attempt needs a new price and connection check; never use an infinite retry loop.

Why should GetLastError be called immediately?

It reports the current _LastError value and resets it. Other operations can change the error state, so a delayed read may describe the wrong call.

Can Pineify fix MQL4 error 136?

Pineify can revise a self-contained .mq4 file, add validation and error logging, and return static MetaEditor diagnostics. It cannot prove broker acceptance, account permissions, market availability, or live execution.

Last verified against the linked official references on . Compile and test the final source in the MetaTrader 4 build, broker, symbol, and account environment you plan to use.

Continue with one reviewable MQL4 file

Define the requirement, inspect the generated source, repair diagnostics, and test the behavior in your own MT4 environment.

Open Coding Agent