BUG ??? Invalid price (10015)
-
Hello friends, I've been trying to understand why my robot is showing this error in the forex market (demo) or (real) for weeks.
New pending order error: Invalid price (10015). Retrying in 5 seconds..
retry #1 of 10
OrderCheck() failed: Invalid price (10015)I'm working with pending buy and sell orders and using the " loop pass "n" times " block to place the amount of orders I want when a certain rule is reached.
The problem I noticed happens when the robot tries to trigger some orders on one side, buy or sell, it generates this error, exceeds the order price (without triggering the order) and abandons the order.
Would this be a BUG????? If yes, broker, mt5 or Fxdreema?
Note: This project I cannot share.
-
Can you please share the link to the project? Apparently it's trying to open to many pending orders.
-
Have you check the price of the pending orders?
-
@sktsec
I didn't understand. What do I have to check? The orders were on the screen, the price went through the orders, they were buy orders so the price of (ask) should trigger them and it didn't trigger this error.
What do you mean by (check pending order price)???
If it is a pending order, then it means that it is already at a certain price on the chart and when the market price reaches it (it should be triggered and become an executed order) or am I wrong? -
@fxDreema you can help here, this is a BUG?
-
@OntradingX said in BUG ??? Invalid price (10015):
@sktsec
I didn't understand. What do I have to check? The orders were on the screen, the price went through the orders, they were buy orders so the price of (ask) should trigger them and it didn't trigger this error.
What do you mean by (check pending order price)???
If it is a pending order, then it means that it is already at a certain price on the chart and when the market price reaches it (it should be triggered and become an executed order) or am I wrong?it is worth checking both "journal" and "expert" tabs
-
@OntradingX
Say, if EA submits a buy pending order with a price higher than the current price, it will response with an error like yours -
@ambrogio it is exactly in these tabs that these errors happen.
The question I want to know is if it could be a problem in some block. -
@OntradingX you should catch the exact time of the issue and do a visual backtest to see what happens at the exact moment the EA places the P.O. As @sktsec says if the pending order (stop or limit) is on the wrong side of the bid/ask it throws the error. This can happen for example when working with price levels based on objects on the chart
-
@ambrogio I understood what you meant.
But I insist on saying and I will give one more very important detail.
This (the) orders that generated this error (were already hanging) were just waiting to be triggered.
The basic principle is that if the order was launched, let's say as it was in the case 1 minute before, then the broker already knew that there was an order there at the price.
Example of how my robot works.- It had sell orders hanging at price 1000, so the market went over there and triggered sell orders at price 1000, all orders were triggered, and at the exact moment these sell orders were triggered, the robot hung others (purchase orders) at price 1300.
The market then went against the sell orders leaving them negative and then he arrived with the ask price at 1300.
In view of all this logic, when the (ask) price reached 1300, he should trigger these orders, correct?
If the answer is yes, then I go further, the ask, bid prices are slowly surpassed at all times giving this mentioned error and (they did not open any orders, I had about 5 orders of 0.01 hanging, I also had enough balance, connection, ticks , everything perfect.
the price stopped there at 1500, that is, I lost 200 profit points because the orders were not triggered.I wanted to understand why the orders were not triggered, I sent an email to the broker and so far I have not had any responses.
In my view, either it is a brokerage problem, or it is a Fxdreema problem (Bug), I can't understand anything about the robot's logic causing this type of error.
It is clear to me that if you have pending buy orders far from ask, as soon as ask reaches the same price as these orders it will trigger these orders, or am I wrong? - It had sell orders hanging at price 1000, so the market went over there and triggered sell orders at price 1000, all orders were triggered, and at the exact moment these sell orders were triggered, the robot hung others (purchase orders) at price 1300.
-
@OntradingX Clear. From the error I saw from the screenshot I understood that the EA doesn't place pending orders. But at this point if you see the pending orders on the chart and also in the list in the MT5/MT4 toolbox it means that the EA has done its job, then it is definitely a problem on the broker side.
-
@OntradingX slippage filter?
-
@ambrogio
I don't have a slippage filter enabled, because I believe there isn't one that works, the fxdreema one I've seen in several posts that the admin mentioned doesn't work.About slippage, I believe that it does not fit this problem, as you agree that slippage would not influence (do not allow opening the order) and yes it would influence improving or worsening the price of the order but (opening) the orders?
-
@OntradingX I really don't know what it could be, sorry, you may find some topics about this error code on mql5 like this
https://www.mql5.com/en/forum/278174
and many others
