WARNING – Different executions same systems

Forums ProRealTime English forum ProOrder support WARNING – Different executions same systems

Viewing 13 posts - 1 through 13 (of 13 total)
  • #8936

    Hey everyone, I found this morning a mistake.

    I started same robot on 2 different accounts, one of them didn’t execute cancel order at the same time, so I’d to remove stop order mannually, as you can see in the attached picture.

    Both robots exited at 09:06:12 with limit orders and after that, only one of them canceled stop order at 09:07:00 and the other had to be closed manually.

    Would this order have been a remaining sell order on market without an stop for that one?

    Strategy link: http://www.prorealcode.com/prorealtime-trading-strategies/alex-autotradingbot-index/

    #8940

    First, are you sure the 2 automated strategies share the same codes? (same version).

    #8943

    Yes, the only difference between them is %risk. Any ideas?

    #8945

    What STOP order? I only see LIMIT ones in the strategy code.

    #8946

    Stop ploss order.

    First line in attached file

    #8949

    Sorry Nicolas… my fault… I sended you to the wrong link strategy…

    Is this one: http://www.prorealcode.com/prorealtime-trading-strategies/dax-trading-strategy-breakoutfakeout/

     

    #8953

    Are these the same ?Screen-Shot-2016-06-07-at-11.33.17-PM

    #8956

    Pending orders need to be set at each new bar, they normally don’t remain on market. So I believe that a variable are stuck in a  state that continuously place a stop order, .. somewhere in the code.. ?

    But I understand that is weird since you are trading the same strategy on 2 different accounts.

    Are we talking about pending orders or stoploss one made by ‘set stop ploss’ instruction?

    #8959

    Not sure but I bet is an stop entry order

    lines 167-169

    if longonmarket then

    if enter2=0 then

    sellshort….

    It should be cancelled after exitted, like the other account did, or maybe the other one should keep it on market if the mistake is in another place.

    like:

    if not onmarket and enter2=0…

    I really don’t know where mistake is atm, but one or another failed coz didn’t do the same with same code.

    Thanks!

    #8960

    Yes they are.

    #8964

    Yes Nicolas, I’m a bit afraid… I started one of them, save, export and import in the other account, checked and changed risk %, that’s all I did. 🙁

    #8973

    It’s a pending order, so if your variable “enter2” is still equal to 0, then this order will remain. The best you can do is to graph all your variables to see if some still have values even if they don’t need to..

    #8979

    Thanks Nicolas, that was what I thought…

    In this case, why the other one closed it at 09:07:00??

    Should keep it open like the other one… We will see tomorrow!

Viewing 13 posts - 1 through 13 (of 13 total)

Create your free account now and post your request to benefit from the help of the community
Register or Login