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. 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.

Open MQL4 Coding AgentReview the code example

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

NoResultOrderModify.mq4MQL4
#property strict
#property script_show_inputs

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

void OnStart()
  {
   if(Ticket <= 0 || StopPoints <= 0)
     {
      Print("A positive ticket and stop distance are required.");
      return;
     }

   ResetLastError();
   if(!OrderSelect(Ticket, SELECT_BY_TICKET))
     {
      int selection_error = GetLastError();
      Print("OrderSelect failed. error=", selection_error);
      return;
     }
   if(OrderCloseTime() != 0 || OrderType() != OP_BUY || OrderSymbol() != Symbol())
     {
      Print("This example only modifies an open buy on the current chart symbol.");
      return;
     }

   RefreshRates();
   if(Bid <= 0.0 || Point <= 0.0)
      return;
   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)
     {
      int modify_error = GetLastError();
      Print("OrderModify failed. error=", modify_error,
            " ticket=", Ticket,
            " stop=", DoubleToString(stop_loss, Digits));
     }
  }
  • Official meaning: no error returned, but the result is unknown
  • Check API results or the runtime failure log
  • Capture relevant inputs and error context
  • 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.

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.

  • 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 accepts only an open buy on the current chart symbol, compares its normalized stop, and skips an unchanged value. It captures failed-call errors immediately. It does not validate stop/freeze distances or a strategy risk policy; test only on a demo ticket you intend to modify.

This script can change the stop of an existing open buy on the current chart symbol. It does not enforce stop/freeze distances or your risk policy. Use only a demo ticket you intend to modify after checking those conditions.

NoResultOrderModify.mq4MQL4
#property strict
#property script_show_inputs

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

void OnStart()
  {
   if(Ticket <= 0 || StopPoints <= 0)
     {
      Print("A positive ticket and stop distance are required.");
      return;
     }

   ResetLastError();
   if(!OrderSelect(Ticket, SELECT_BY_TICKET))
     {
      int selection_error = GetLastError();
      Print("OrderSelect failed. error=", selection_error);
      return;
     }
   if(OrderCloseTime() != 0 || OrderType() != OP_BUY || OrderSymbol() != Symbol())
     {
      Print("This example only modifies an open buy on the current chart symbol.");
      return;
     }

   RefreshRates();
   if(Bid <= 0.0 || Point <= 0.0)
      return;
   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)
     {
      int modify_error = GetLastError();
      Print("OrderModify failed. error=", modify_error,
            " ticket=", Ticket,
            " 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

    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 1 and the inputs relevant to the failed 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. Use the API result or critical runtime log, together with the relevant inputs, to identify the failed operation.

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?

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 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.

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