MQL4 ERR_REQUOTE
MT4 error 138 requote maps to ERR_REQUOTE: requote. The requested market price is fully out of date, so the server offers or requires a newer price. Capture GetLastError immediately after the failed call, correct the cause, and retry only when the condition can change.
#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));
}The official MQL4 runtime table names error 138 ERR_REQUOTE and defines it as “requote.” The requested market price is fully out of date, so the server offers or requires a newer price.
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.
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.
A small bounded retry is appropriate only after a fresh quote and a new entry-rule check. Stop if the allowed attempt or time budget is exhausted.
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.
| Check | Action |
|---|---|
| The EA submits an old Bid or Ask after calculation or latency | Call RefreshRates and rebuild the order from the current side of the quote. |
| The market moved outside the allowed slippage before the request arrived | Keep slippage explicit and consistent with the strategy rather than widening it silently. |
| A different symbol price was used for the order | Read the quote for the exact order symbol. |
| The retry path reuses the rejected price | Use a bounded attempt count and create a new price for each attempt. |
The script refreshes rates and creates the request price immediately before OrderSend. A production retry must recheck the signal and risk rule, not just the price.
The example improves validation and logging. It does not prove the operation will be accepted by a broker or behave safely in live trading.
#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));
}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 AgentStatic diagnostics do not prove runtime behavior, backtest results, broker compatibility, or live-trading safety.
Check the API return value before interpreting an error number from the log.
Call GetLastError immediately and record error 138, symbol, prices, volume, ticket, and terminal state relevant to the operation.
Call RefreshRates and rebuild the order from the current side of the quote.
Compile the revised source, then test with the same MT4 build, broker, symbol, account permissions, and market state.
ERR_REQUOTE means requote. The code should still identify which API returned failure and log the inputs used for that call.
The EA submits an old Bid or Ask after calculation or latency The market moved outside the allowed slippage before the request arrived A different symbol price was used for the order The retry path reuses the rejected price
A small bounded retry is appropriate only after a fresh quote and a new entry-rule check. Stop if the allowed attempt or time budget is exhausted.
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.
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.
Define the requirement, inspect the generated source, repair diagnostics, and test the behavior in your own MT4 environment.
Open Coding Agent