Broker API HubMenu

MetaTrader 5 trade server return code

MetaTrader 5 trade server return code: 10039 TRADE_RETCODE_CLOSE_ORDER_EXIST

The error, as text you can copy

10039 TRADE_RETCODE_CLOSE_ORDER_EXIST
Kind
Trade server return code
Where you meet it
Returned by the trade server to the platform
API
MetaTrader 5 (Python package and MQL5)

What does 10039 TRADE_RETCODE_CLOSE_ORDER_EXIST mean on the MetaTrader 5 API?

A close order already exists for the position. The vendor says this can happen on hedging accounts in two cases: closing a position with an opposite one when close orders for it already exist, or closing all or part of a position when the existing close orders and the new one together exceed the position's volume. It is a MetaTrader 5 trade server return code, placed in the retcode field of the MqlTradeResult structure after OrderSend().

Risk warning: CFDs and spread bets are complex instruments and come with a high risk of losing money rapidly due to leverage. You can lose money on these products, and each provider publishes its own loss figure under FCA rules. You should consider whether you understand how they work and whether you can afford to take the high risk of losing your money. Automated and API trading can amplify losses through bugs, connectivity failures and runaway orders.

Independent and unofficialmql5.comchecked

How do I fix 10039 TRADE_RETCODE_CLOSE_ORDER_EXIST?

The vendor's page gives no remedy. It follows from the meaning that the existing close orders for the position should be checked before another is sent.