Pineify logo

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. For API calls, check the return value and capture GetLastError after a documented failure. Critical runtime errors require preventive guards and inspection of the terminal log.

See where Pineify fitsReview the code example
OffQuotesDiagnostic.mq4MQL4
#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
  • Check API results or the runtime failure log
  • Capture relevant inputs and error context
  • 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.

An error-state value is supporting context, not proof that a call failed or a diagnosis of the whole EA. For noncritical API failures, read the return value and then GetLastError, which resets _LastError. Critical errors such as zero division terminate execution, so code after the failing expression cannot serve as a recovery handler.

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

Retry only within a fixed attempt/time budget after checking quote freshness, connection, and the original signal and risk limits. RefreshRates alone does not prove a new executable quote is available.

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 and records the requested Ask on failure. It has no quote-age check or retry loop; add those checks together with signal, risk, and duplicate-order controls before demo use.

This script can submit one market buy with no SL or TP. It omits volume, margin, quote-freshness, and duplicate-order controls. Add the required controls and use only a demo account before evaluating this diagnostic.

OffQuotesDiagnostic.mq4MQL4
#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

    Locate the failed operation

    Check the API result, or the terminal log and source location for a critical runtime failure.

  2. 2

    Capture the error once

    For a recoverable API failure, capture GetLastError immediately. For a terminated program, preserve the terminal log. Record error 136 and the inputs relevant to the failed 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. Use the API result or critical runtime log, together with the relevant inputs, to identify the failed operation.

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?

Retry only within a fixed attempt/time budget after checking quote freshness, connection, and the original signal and risk limits. RefreshRates alone does not prove a new executable quote is available.

Why should GetLastError be called immediately?

For a noncritical API failure it reports the current _LastError value and resets it. A delayed read may describe another call. It cannot recover execution after a critical error has terminated the program.

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.

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