Pineify logo

MQL5 trade server return code

MQL5 Error 10018: Market closed

MQL5 error 10018 is TRADE_RETCODE_MARKET_CLOSED, the official trade server return code for market closed. Read the symbol trade sessions in server time and submit only during an open session. Handle holidays, maintenance, and instrument-specific breaks as unavailable states instead of running an immediate retry loop. Read MqlTradeResult.retcode after OrderSend because a successful function return does not by itself mean that the order was executed.

Open MQL5 Coding AgentReview the diagnostic example

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

Check retcode 10018.mq5
bool HasTradeSessionToday(const string symbol)
  {
   MqlDateTime now={};
   TimeToStruct(TimeTradeServer(),now);
   datetime from=0,to=0;

   for(uint index=0;
       SymbolInfoSessionTrade(symbol,(ENUM_DAY_OF_WEEK)now.day_of_week,index,from,to);
       index++)
      PrintFormat("session %u: %s to %s",index,TimeToString(from,TIME_MINUTES),
                  TimeToString(to,TIME_MINUTES));

   return index>0;
  }
  • Official code: TRADE_RETCODE_MARKET_CLOSED
  • Meaning: Market closed
  • Layer: trade server response
  • Verify: MqlTradeResult.retcode

Also searched as: mql5 error code err_market_closed; mql5 error constants err_market_closed.

What error 10018 actually reports

The code belongs to MqlTradeResult.retcode, not to the compiler error list and not necessarily to GetLastError. The trade server uses 10018 to report market closed.

Keep the request, the boolean returned by OrderSend, result.retcode, result.comment, and the symbol properties in the same log record. That separates a client-side request failure from a server-side rejection.

Inspect the request before changing the strategy

Use the smallest failing order and compare every broker-sensitive value with the current symbol and account. Do not hide the error by retrying unchanged input.

  • Use SymbolInfoSessionTrade for the requested weekday and session index.
  • Compare with TimeTradeServer rather than assuming local computer time.
  • Confirm the exact symbol is selected and has a current quote.
  • Back off until the next valid session instead of repeating the rejected request.

Repair and verify

Read the symbol trade sessions in server time and submit only during an open session. Handle holidays, maintenance, and instrument-specific breaks as unavailable states instead of running an immediate retry loop.

Run OrderCheck with the completed request, log its retcode and comment, then send only if the check is acceptable. OrderCheck improves diagnostics but does not guarantee execution.

Use a focused diagnostic

The loop enumerates the broker-defined trade sessions for the current server weekday. Production code also needs to compare the current server time with each interval and handle sessions crossing midnight.

A valid request can still be rejected or filled differently by the trade server. Check the returned retcode, test with the broker symbol and account, and review risk before any live order.

Check retcode 10018.mq5
bool HasTradeSessionToday(const string symbol)
  {
   MqlDateTime now={};
   TimeToStruct(TimeTradeServer(),now);
   datetime from=0,to=0;

   for(uint index=0;
       SymbolInfoSessionTrade(symbol,(ENUM_DAY_OF_WEEK)now.day_of_week,index,from,to);
       index++)
      PrintFormat("session %u: %s to %s",index,TimeToString(from,TIME_MINUTES),
                  TimeToString(to,TIME_MINUTES));

   return index>0;
  }
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

    Capture the complete result

    Log the OrderSend return value, result.retcode, result.comment, symbol, order type, volume, price, stops, and filling mode. Confirm that the retcode is 10018.

  2. 2

    Read current constraints

    Query the symbol and account immediately before building the request. Broker constraints can differ between symbols and sessions.

  3. 3

    Change the invalid field

    Read the symbol trade sessions in server time and submit only during an open session. Handle holidays, maintenance, and instrument-specific breaks as unavailable states instead of running an immediate retry loop.

  4. 4

    Check, send, and retest

    Call OrderCheck, submit the corrected request, then reproduce it in Strategy Tester and a demo account before considering live use.

Frequently asked questions

What does MQL5 error 10018 mean?

It is TRADE_RETCODE_MARKET_CLOSED, the official MQL5 trade server return code for market closed.

Is 10018 a GetLastError code?

Treat it as a trade server return code when it appears in MqlTradeResult.retcode. GetLastError reports the terminal runtime error layer, which is a separate diagnostic channel.

Does OrderSend returning true mean the trade executed?

No. The official OrderSend reference says true means the request passed basic checks and was accepted for processing. Inspect result.retcode and subsequent trade events to determine the outcome.

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