MQL4 ERR_FUNCTION_NOT_ALLOWED
MQL4 error 4060 function not allowed for call maps to ERR_FUNCTION_NOT_ALLOWED: function is not allowed for call. The operation is unavailable from the current MQL4 program type, handler, tester mode, or terminal context. 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 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));
}The official MQL4 runtime table names error 4060 ERR_FUNCTION_NOT_ALLOWED 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.
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 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.
| Check | Action |
|---|---|
| The API is called from an unsupported program type or event handler | Read the API restrictions and identify the permitted program context. |
| A synchronous operation is attempted from a restricted runtime context | Move the operation to a supported handler or a separate program. |
| Strategy Tester does not support the same operation as a live chart | Add an explicit tester or runtime branch when behavior differs. |
| Shared helper code ignores whether it runs in an EA, indicator, or script | Keep context-dependent calls out of helpers that cannot verify their caller. |
The script keeps its operation inside OnStart and validates inputs before the call. Replace the sample with the failing API and move it to a context documented to support that function.
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 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));
}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 4060, symbol, prices, volume, ticket, and terminal state relevant to the operation.
Read the API restrictions and identify the permitted program context.
Compile the revised source, then test with the same MT4 build, broker, symbol, account permissions, and market state.
ERR_FUNCTION_NOT_ALLOWED means function is not allowed for call. The code should still identify which API returned failure and log the inputs used for that call.
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
Do not retry in the same prohibited context. The program type, handler, or environment must change.
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