Pineify logo

MQL4 ERR_NO_RESULT

MQL4 error 1: no result from an unchanged request

MQL4 error 1 maps to ERR_NO_RESULT: no error returned, but the result is unknown. OrderModify can return error 1 when the supplied values are unchanged, so compare the current order fields before sending a modification. Capture GetLastError immediately after the failed call, correct the cause, and retry only when the condition can change.

Open MQL4 Coding AgentReview the code example

Open the Coding Agent, then choose MQL4 from the language menu.

NoResultOrderModify.mq4.mq4
#property strict
#property script_show_inputs

input int Ticket = 0;
input int StopPoints = 200;

void OnStart()
  {
   if(Ticket <= 0 || !OrderSelect(Ticket, SELECT_BY_TICKET))
     {
      Print("OrderSelect failed. error=", GetLastError());
      return;
     }

   RefreshRates();
   double stop_loss = NormalizeDouble(Bid - StopPoints * Point, Digits);
   if(MathAbs(OrderStopLoss() - stop_loss) < Point / 2.0)
     {
      Print("No OrderModify call: the stop loss is unchanged.");
      return;
     }

   ResetLastError();
   bool changed = OrderModify(OrderTicket(), OrderOpenPrice(), stop_loss,
                              OrderTakeProfit(), 0, clrNONE);
   if(!changed)
      Print("OrderModify failed. error=", GetLastError(),
            " ticket=", OrderTicket(),
            " stop=", DoubleToString(stop_loss, Digits));
  }
  • Official meaning: no error returned, but the result is unknown
  • Read the failed API return value first
  • Capture GetLastError immediately
  • Retry only when the condition can change

What MQL4 error 1 means

The official MQL4 runtime table names error 1 ERR_NO_RESULT and defines it as “no error returned, but the result is unknown.” OrderModify can return error 1 when the supplied values are unchanged, so compare the current order fields before sending a modification.

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.

  • OrderModify receives the same price, stop loss, take profit, and expiration
  • Rounding makes a proposed value equal to the current order value
  • The code reads a stale error without first confirming the call failed
  • The EA treats an unknown result as proof that a modification succeeded

Fix the cause, then choose a retry policy

Do not resend an unchanged modification. Verify the selected order, calculate a genuinely different valid value, and make one new request.

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
OrderModify receives the same price, stop loss, take profit, and expirationCompare every modifiable field and skip the call when no value changed.
Rounding makes a proposed value equal to the current order valueNormalize prices before performing the comparison.
The code reads a stale error without first confirming the call failedReset the error, call OrderModify, and read GetLastError only on false.
The EA treats an unknown result as proof that a modification succeededRe-select the order and verify server state when the result remains uncertain.

Review the complete example

The script compares the normalized stop with the current stop and avoids an unchanged OrderModify request. It captures the error only when the call returns false.

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

NoResultOrderModify.mq4.mq4
#property strict
#property script_show_inputs

input int Ticket = 0;
input int StopPoints = 200;

void OnStart()
  {
   if(Ticket <= 0 || !OrderSelect(Ticket, SELECT_BY_TICKET))
     {
      Print("OrderSelect failed. error=", GetLastError());
      return;
     }

   RefreshRates();
   double stop_loss = NormalizeDouble(Bid - StopPoints * Point, Digits);
   if(MathAbs(OrderStopLoss() - stop_loss) < Point / 2.0)
     {
      Print("No OrderModify call: the stop loss is unchanged.");
      return;
     }

   ResetLastError();
   bool changed = OrderModify(OrderTicket(), OrderOpenPrice(), stop_loss,
                              OrderTakeProfit(), 0, clrNONE);
   if(!changed)
      Print("OrderModify failed. error=", GetLastError(),
            " ticket=", OrderTicket(),
            " stop=", DoubleToString(stop_loss, 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 1, symbol, prices, volume, ticket, and terminal state relevant to the operation.

  3. 3

    Correct the triggering condition

    Compare every modifiable field and skip the call when no value changed.

  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 1 mean?

ERR_NO_RESULT means no error returned, but the result is unknown. The code should still identify which API returned failure and log the inputs used for that call.

What usually causes MQL4 error 1?

OrderModify receives the same price, stop loss, take profit, and expiration Rounding makes a proposed value equal to the current order value The code reads a stale error without first confirming the call failed The EA treats an unknown result as proof that a modification succeeded

Should an EA retry after error 1?

Do not resend an unchanged modification. Verify the selected order, calculate a genuinely different valid value, and make one new request.

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 1?

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