Pineify logo

MQL4 ERR_FUNCTION_NOT_CONFIRMED

MQL4 error 4060: move the call to a valid context

MQL4 error 4060 function not allowed for call maps to ERR_FUNCTION_NOT_CONFIRMED: function is not allowed for call. The operation is unavailable from the current MQL4 program type, handler, tester mode, or terminal context. 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.

ContextGuard.mq4MQL4
#property strict
#property script_show_inputs

input int Period = 14;

void OnStart()
  {
   if(Period < 1 || Bars <= Period)
     {
      Print("Invalid period or insufficient history: ", Period);
      return;
     }

   ResetLastError();
   double value = iMA(NULL, 0, Period, 0, MODE_SMA, PRICE_CLOSE, 1);
   int error_code = GetLastError();
   if(error_code != 0)
     {
      Print("iMA failed. error=", error_code);
      return;
     }

   Print("SMA: ", DoubleToString(value, Digits));
  }
  • Official meaning: function is not allowed for call
  • Check API results or the runtime failure log
  • Capture relevant inputs and error context
  • Retry only when the condition can change

What MQL4 error 4060 means

The official MQL4 runtime table names error 4060 ERR_FUNCTION_NOT_CONFIRMED and defines it as “function is not allowed for call.” The operation is unavailable from the current MQL4 program type, handler, tester mode, or terminal context.

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.

  • The API is called from an unsupported program type or event handler
  • A synchronous operation is attempted from a restricted runtime context
  • Strategy Tester does not support the same operation as a live chart
  • Shared helper code ignores whether it runs in an EA, indicator, or script

Fix the cause, then choose a retry policy

Do not retry in the same prohibited context. The program type, handler, or environment must change.

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
The API is called from an unsupported program type or event handlerRead the API restrictions and identify the permitted program context.
A synchronous operation is attempted from a restricted runtime contextMove the operation to a supported handler or a separate program.
Strategy Tester does not support the same operation as a live chartAdd an explicit tester or runtime branch when behavior differs.
Shared helper code ignores whether it runs in an EA, indicator, or scriptKeep context-dependent calls out of helpers that cannot verify their caller.

Review the complete example

This script validates an iMA call; it does not reproduce 4060 or make every API legal in OnStart. A concrete 4060 case is WebRequest called from an indicator: move that work to a permitted EA or script. WebRequest also cannot run in Strategy Tester.

The example improves validation and logging. It does not prove the operation will be accepted by a broker or behave safely in live trading.

ContextGuard.mq4MQL4
#property strict
#property script_show_inputs

input int Period = 14;

void OnStart()
  {
   if(Period < 1 || Bars <= Period)
     {
      Print("Invalid period or insufficient history: ", Period);
      return;
     }

   ResetLastError();
   double value = iMA(NULL, 0, Period, 0, MODE_SMA, PRICE_CLOSE, 1);
   int error_code = GetLastError();
   if(error_code != 0)
     {
      Print("iMA failed. error=", error_code);
      return;
     }

   Print("SMA: ", DoubleToString(value, 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 4060 and the inputs relevant to the failed operation.

  3. 3

    Correct the triggering condition

    Read the API restrictions and identify the permitted program context.

  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 4060 function not allowed for call mean?

ERR_FUNCTION_NOT_CONFIRMED means function is not allowed for call. Use the API result or critical runtime log, together with the relevant inputs, to identify the failed operation.

What usually causes MQL4 error 4060?

The API is called from an unsupported program type or event handler. A synchronous operation is attempted from a restricted runtime context. Strategy Tester does not support the same operation as a live chart. Shared helper code ignores whether it runs in an EA, indicator, or script.

Should an EA retry after error 4060?

Do not retry in the same prohibited context. The program type, handler, or environment must change.

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

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