And another question: how is it possible to get off quote errors for pending orders?
Thanks.
Yes, the market was open (the time was gmt+2). Is it possible that there is something wrong with the demo account?
Thanks.
It's actually a new demo account (ducascopy, fair trading technologies). I developed the EA for a client and he's trying the functionality on a number of different demo-accounts. I think only the ducascopy demo-account has this problem.
Thanks!
The pending order gets placed at the start of a new bar at a specified number of pips lower/higher than the low/high of the previous bar. I assumed that the client would use a number of pips greater than the minimum distance for this value, the check is not explicitly made. I now perform the check in my last version.
However, if this was the problem then there would be an error 130 or maybe an error 3 but not the off quotes error. I am backtesting the (previous: no distance check) EA for the broker were the problem occured, but the strategytester does not show any errors.
Thanks!
Sorry, what do you mean exactly? I don't know what "the ST" is?
thanks
Oh right.. strategytester; my bad :) it can give the 130 and 3 errors but not the off quotes indeed.
Still.. what to do about the off quotes? How is it possible that this error occurs for pending orders?
Thanks!

- Free trading apps
- Over 8,000 signals for copying
- Economic news for exploring financial markets
You agree to website policy and terms of use
Hi,
the error messages below were generated in the journal while an EA was trying to place pending orders. Error 136 (off quotes) is captured by waiting for the refreshrates() in a loop and immediately sending the order again with the new prices; However, the process below keeps repeating itself. The EA works fine on other platforms; The message below was generated in a new dusascopy ecn demo account. Is there something wrong with the demo account or do I need to handle the error differently?
Thanks!