MQL4 ERR_OBJECT_ALREADY_EXISTS

Error 4200 MQL4: use a unique chart object name

error 4200 MQL4 object already exists maps to ERR_OBJECT_ALREADY_EXISTS: object already exists. ObjectCreate was asked to create a chart object whose name already exists in the target chart. 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 Agent Review the code example

Open the Coding Agent, then choose MQL4 from the language menu.

UniqueChartObject.mq4MQL4

#property strict

void OnStart()
  {
   string object_name = "pineify_diagnostic_line";
   if(ObjectFind(0, object_name) >= 0)
     {
      Print("Object already exists: ", object_name);
      return;
     }

   ResetLastError();
   if(!ObjectCreate(0, object_name, OBJ_HLINE, 0, 0, Bid))
     {
      Print("ObjectCreate failed. error=", GetLastError());
      return;
     }

   ChartRedraw(0);
  }

Official meaning: object already exists
Check API results or the runtime failure log
Capture relevant inputs and error context
Retry only when the condition can change

What MQL4 error 4200 means

The official MQL4 runtime table names error 4200 ERR_OBJECT_ALREADY_EXISTS and defines it as “object already exists.” ObjectCreate was asked to create a chart object whose name already exists in the target chart.

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.

OnInit or OnCalculate recreates the same object name
Multiple indicator instances share a fixed object name
Old objects remain after removal or template changes
The code does not check ObjectFind before ObjectCreate

Fix the cause, then choose a retry policy

Do not call ObjectCreate again with the same name. Update, delete, or rename the existing object first.

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
OnInit or OnCalculate recreates the same object name	Check for the object before creating it.
Multiple indicator instances share a fixed object name	Include chart, symbol, timeframe, or instance identity in the name.
Old objects remain after removal or template changes	Update an existing object when reuse is intended.
The code does not check ObjectFind before ObjectCreate	Delete only objects owned by the program during cleanup.

Review the complete example

The script skips an existing name and otherwise creates a line on the current chart. It does not generate a unique name per instance or check quote freshness; add those controls if multiple instances or price-sensitive placement are required.

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

UniqueChartObject.mq4MQL4

#property strict

void OnStart()
  {
   string object_name = "pineify_diagnostic_line";
   if(ObjectFind(0, object_name) >= 0)
     {
      Print("Object already exists: ", object_name);
      return;
     }

   ResetLastError();
   if(!ObjectCreate(0, object_name, OBJ_HLINE, 0, 0, Bid))
     {
      Print("ObjectCreate failed. error=", GetLastError());
      return;
     }

   ChartRedraw(0);
  }

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
Locate the failed operation
Check the API result, or the terminal log and source location for a critical runtime failure.
2
Capture the error once
For a recoverable API failure, capture GetLastError immediately. For a terminated program, preserve the terminal log. Record error 4200 and the inputs relevant to the failed operation.
3
Correct the triggering condition
Check for the object before creating it.
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 error 4200 MQL4 object already exists mean?

ERR_OBJECT_ALREADY_EXISTS means object already exists. Use the API result or critical runtime log, together with the relevant inputs, to identify the failed operation.

What usually causes MQL4 error 4200?

OnInit or OnCalculate recreates the same object name. Multiple indicator instances share a fixed object name. Old objects remain after removal or template changes. The code does not check ObjectFind before ObjectCreate.

Should an EA retry after error 4200?

Do not call ObjectCreate again with the same name. Update, delete, or rename the existing object first.

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

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.

Official references

Related MQL4 resources

MQL4 error code reference Error handling in MQL4 MQL4 AI Coding Agent

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