MT4 error 130: Invalid stops

What MQL4 says

130 ERR_INVALID_STOPS

Invalid stops

From MQL4's table of error codes, read 24 October 2026. An Expert Advisor reads it with GetLastError() after a call fails; the Experts and Journal tabs print what the EA logs.

What causes it

A stop loss or take profit is closer to the market than the broker's minimum distance, or isn't normalized; for a pending order, the open price itself is too close. MQL4's OrderSend page gives the minimum as MarketInfo() with MODE_STOPLEVEL, in points, and warns that a stop level of 0 can mean a floating limit the terminal can't see.

How to fix it

Keep stops at least MODE_STOPLEVEL points from the market. Read MarketInfo(Symbol(), MODE_STOPLEVEL), measure a buy's stop loss and take profit from Bid and a sell's from Ask (the MQL4 Book's StopLevel table), normalize each level to Digits with NormalizeDouble(), and leave extra room when the stop level reads 0.

Source: MQL4 Reference: OrderSend. No MQL4 code is shown because none here was compiled; adapt the steps to your EA.

The same error in MT5

MT5 returns it as a trade server code instead: MT5 error 10016: Invalid stops in the request.

Other MT4 errors

• MT4 error 0: No error returned
• MT4 error 1: No error returned, but the result is unknown
• MT4 error 2: Common error
• MT4 error 3: Invalid trade parameters
• MT4 error 131: Invalid trade volume
• MT4 error 132: Market is closed
• MT4 error 133: Trade is disabled
• MT4 error 134: Not enough money
• MT4 error 136: Off quotes
• MT4 error 4051: Invalid function parameter value
• MT4 error 4107: Invalid price
• MT4 error 4111: Shorts are not allowed
• MT4 error 4112: Automated trading by Expert Advisors/Scripts disabled by trade server
• MT4 error 4200: Object already exists
• MT4 error 5004: Cannot open file