Pineify logo

MQL5 runtime error reference

MQL5 Error 4301: Unknown symbol

MQL5 error 4301 officially means "Unknown symbol." A symbol API received a name that the connected terminal does not recognize, often because code used a generic name instead of the broker-specific symbol. Use the exact name from the terminal, select it with SymbolSelect when appropriate, and stop if the broker does not provide that instrument. Do not guess suffixes in live order code. Capture GetLastError immediately around the failing call so an older error is not mistaken for the current failure.

Open MQL5 Coding AgentReview the diagnostic example

Open the Coding Agent and choose MQL5 from the language menu.

Isolate runtime error 4301.mq5
bool PrepareSymbol(const string symbol)
  {
   ResetLastError();
   if(!SymbolSelect(symbol,true))
     {
      PrintFormat("Unknown or unavailable symbol [%s], error=%d",
                  symbol,GetLastError());
      return false;
     }
   return true;
  }
  • Official meaning: Unknown symbol
  • Layer: terminal runtime
  • Read with: GetLastError
  • First step: isolate the failing call

Where error 4301 comes from

A symbol API received a name that the connected terminal does not recognize, often because code used a generic name instead of the broker-specific symbol. The numeric value is listed in the official runtime error table, which is separate from MetaEditor compilation errors and trade server return codes.

Reset the last-error state before the suspected call, save its direct return value, and read GetLastError immediately afterward. This produces a causal log instead of a stale code.

Checks that narrow the cause

Preserve the exact parameters and terminal context that produced the failure. Check one precondition at a time before adding retries.

  • Print the symbol string with delimiters to expose whitespace.
  • Compare against SymbolsTotal and SymbolName results.
  • Call SymbolSelect(symbol, true) and inspect its return value.
  • Use _Symbol when the intended instrument is the current chart symbol.

Apply the smallest repair

Use the exact name from the terminal, select it with SymbolSelect when appropriate, and stop if the broker does not provide that instrument. Do not guess suffixes in live order code.

After the repair, test both the expected path and a deliberately invalid input. The second test confirms that the diagnostic branch still exposes failures.

Use a focused diagnostic

The check makes the exact requested name visible and selects it through the terminal. Failure remains actionable instead of silently substituting another instrument.

A clean compile or a cleared error code does not prove strategy logic, broker compatibility, backtest quality, or live-trading safety. Reproduce the result in the target MetaTrader 5 terminal and account environment.

Isolate runtime error 4301.mq5
bool PrepareSymbol(const string symbol)
  {
   ResetLastError();
   if(!SymbolSelect(symbol,true))
     {
      PrintFormat("Unknown or unavailable symbol [%s], error=%d",
                  symbol,GetLastError());
      return false;
     }
   return true;
  }
Where Pineify fits

Repair editable MQL5 source with compiler feedback

Pineify can generate or revise MQL5 source and use MQL5 compilation diagnostics during the coding workflow. Keep the exact error, source location, program type, and intended behavior in the request so the change remains reviewable.

Open MQL5 Coding Agent

Pineify does not run your broker terminal, Strategy Tester, market data, or live orders. Validate the final program in your own MetaTrader 5 environment.

Review MQL5 AI Coding Agent capabilities
Pineify MQL5 AI Coding Agent with an editable MetaTrader 5 code artifact

A practical verification workflow

  1. 1

    Reset the error state

    Call ResetLastError directly before the suspected function so the next code belongs to that operation.

  2. 2

    Record call and inputs

    Save the function return value, every input, and GetLastError. Confirm that the captured runtime code is 4301.

  3. 3

    Validate the preconditions

    Print the symbol string with delimiters to expose whitespace. Compare against SymbolsTotal and SymbolName results. Call SymbolSelect(symbol, true) and inspect its return value. Use _Symbol when the intended instrument is the current chart symbol.

  4. 4

    Retest in the target terminal

    Compile the changed source, repeat the failing operation, and test the surrounding EA or indicator behavior in MetaTrader 5.

Frequently asked questions

What does MQL5 error 4301 mean?

The official runtime error table defines 4301 as "Unknown symbol."

Is error 4301 a compiler error?

No in this context. It is a terminal runtime code. Compiler diagnostics and MqlTradeResult.retcode values use separate code tables.

Why should I call ResetLastError first?

The terminal stores the last runtime error. Resetting it before the suspected call makes the following GetLastError value easier to attribute to that call.

Last verified against the linked official references on . Compile and test the final source in the MetaTrader 5 build, broker, symbol, and account environment you plan to use.

Continue with reviewable MQL5 source

Provide the exact diagnostic and intended behavior, inspect the generated change, compile it, and verify it in your MT5 test environment.

Open MQL5 Coding Agent