MQL4 ERR_INVALID_STOPS
MQL4 error 130 invalid stops maps to ERR_INVALID_STOPS: invalid stops. A stop loss, take profit, or pending-order price is invalid, unnormalized, or too close to the market under the server rules. Capture GetLastError immediately after the failed call, correct the cause, and retry only when the condition can change.
Open the Coding Agent, then choose MQL4 from the language menu.
#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));
}The official MQL4 runtime table names error 130 ERR_INVALID_STOPS and defines it as “invalid stops.” A stop loss, take profit, or pending-order price is invalid, unnormalized, or too close to the market under the server rules.
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.
Do not retry unchanged invalid prices. Recalculate them from a fresh quote and current broker limits, then send one corrected 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.
| Check | Action |
|---|---|
| Stop loss or take profit is on the wrong side of Bid or Ask | Validate the direction of every stop against the current Bid and Ask. |
| The price is closer than MODE_STOPLEVEL or the server floating limit | Read MODE_STOPLEVEL and allow for a server-side floating restriction even when it reports zero. |
| A price was not normalized to the symbol digits or tick size | Normalize request prices for the target symbol before sending them. |
| OrderModify crosses a stop or freeze restriction as the quote moves | Refresh the quote and recheck stop and freeze distances just before the request. |
The script selects a ticket, normalizes the new stop, skips an unchanged value, and logs a failed OrderModify. Add explicit stop-level and freeze-level checks for the target symbol before live use.
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 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));
}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 130, symbol, prices, volume, ticket, and terminal state relevant to the operation.
Validate the direction of every stop against the current Bid and Ask.
Compile the revised source, then test with the same MT4 build, broker, symbol, account permissions, and market state.
ERR_INVALID_STOPS means invalid stops. The code should still identify which API returned failure and log the inputs used for that call.
Stop loss or take profit is on the wrong side of Bid or Ask The price is closer than MODE_STOPLEVEL or the server floating limit A price was not normalized to the symbol digits or tick size OrderModify crosses a stop or freeze restriction as the quote moves
Do not retry unchanged invalid prices. Recalculate them from a fresh quote and current broker limits, then send one corrected request.
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