Pineify logo

MQL4 ERR_NOT_ENOUGH_MONEY

MQL4 error 134 not enough money: causes and fixes

MQL4 error 134 not enough money maps to ERR_NOT_ENOUGH_MONEY: not enough money. The server rejected the trade because the account did not have enough free margin for the requested symbol, volume, and order type. 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.

OrderSendMarginDiagnostic.mq4MQL4
#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));
  }
  • Official meaning: not enough money
  • Check API results or the runtime failure log
  • Capture relevant inputs and error context
  • Retry only when the condition can change

What MQL4 error 134 means

The official MQL4 runtime table names error 134 ERR_NOT_ENOUGH_MONEY and defines it as “not enough money.” The server rejected the trade because the account did not have enough free margin for the requested symbol, volume, and order type.

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.

  • Requested lots require more margin than the account has free
  • The EA uses a stale balance, equity, price, or margin assumption
  • Symbol contract size, leverage, or margin mode differs from the test setup
  • Other open positions or pending orders already consume margin

Fix the cause, then choose a retry policy

Do not resend the same volume immediately. Recalculate free margin and volume first; retry only if the sizing rule now passes without increasing the intended risk.

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
Requested lots require more margin than the account has freeCalculate a smaller valid volume and reject the trade when the margin check fails.
The EA uses a stale balance, equity, price, or margin assumptionRefresh account and quote inputs immediately before sizing the order.
Symbol contract size, leverage, or margin mode differs from the test setupRead the live symbol and account properties instead of copying test assumptions.
Other open positions or pending orders already consume marginInclude existing exposure in the sizing rule and do not increase risk to force acceptance.

Review the complete example

The script attempts one market buy and logs the error, symbol, rounded lots, and Ask if OrderSend fails. It neither logs every request field nor checks free margin. Add account-specific margin and volume checks before any demo order.

This script can submit one market buy with no SL or TP. It omits volume, margin, quote-freshness, and duplicate-order controls. Add the required controls and use only a demo account before evaluating this diagnostic.

OrderSendMarginDiagnostic.mq4MQL4
#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));
  }
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 134 and the inputs relevant to the failed operation.

  3. 3

    Correct the triggering condition

    Calculate a smaller valid volume and reject the trade when the margin check fails.

  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 134 not enough money mean?

ERR_NOT_ENOUGH_MONEY means not enough money. Use the API result or critical runtime log, together with the relevant inputs, to identify the failed operation.

What usually causes MQL4 error 134?

Requested lots require more margin than the account has free. The EA uses a stale balance, equity, price, or margin assumption. Symbol contract size, leverage, or margin mode differs from the test setup. Other open positions or pending orders already consume margin.

Should an EA retry after error 134?

Do not resend the same volume immediately. Recalculate free margin and volume first; retry only if the sizing rule now passes without increasing the intended risk.

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

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