Reject – Another Order same Position

Forums ProRealTime English forum ProRealTime platform support Reject – Another Order same Position

Viewing 15 posts - 1 through 15 (of 28 total)
  • #81506

    Anybody cast any intelligence on what the attached Reject message means?

    I have had it loads and loads over the years, but never really understood what it means.

    Is it referring to another Order on another System or is my System that got rejected trying to execute 2 Orders at the same time!!??

     

    #81649

    Sorry but I don’t know, I’m thinking of another order already on its way to be written in their order books, so the one sent by this strategy have to wait.. BTW you should call them to discuss 😆

    1 user thanked author for this post.
    #81660

    Hi GraHam,

    it’s quite difficult for us to analyze this message without a technical report and your orders.

    If this error message persists, please send a technical report.

    Regards,

    Jakub

    #81697

    All 5 of the Orders showing as Rejected are for the reason I highlight in this Topic.

    How does one reference / refer to an order in a Technical Report? I ask because Orders don’t have individual numbers / unique identifier??

    Do you want me to send in a Technical Report stating the System and a date / time of the Order?

    EDIT / PS

    It’s crazy really as one would think that an error message using specific words (as this one) would have a certain set of conditions that triggered it??

    It seems like we start from square one / 1st base every time as if nobody has ever seen such an error message before??  I’ve had this same error message many dozens (100’s even)  of times over the years.

    #81734

    I can say that this kind of message is sent by IG server and is generic for many different reason. That’s why, if you want to find out why it has fired, further investigation is needed..

    #81745

    I’ve had this same error message many dozens (100’s even)  of times over the years.

    Me too.

    #81929

    +1 more times than I care to remember and also have never known what it means but in the true spirit of trying to use PRT I accept it for whatever it is keep smiling and carry on… – I think there are major issues with orders being sent from PRT to IG in terms of order acknowledgment/confirmation response times so on occasion for whatever reason the same order is sent by the code but IG says ‘hang on we’re already trying to process the same order you just sent’ and PRT says oh ok in that case I’ll bomb out the strategy (I posted something about this long time back in terms of what I was experiencing running strategies on the 1 second timeframe but for some reason can’t find the thread but was looking forward to ITF’s reply… will have another dig)

    #81930

    Hi Max, how you doing, glad to see you back in these parts! 🙂

    keep smiling and carry on

    It’s all making me give up, I only wish I had your sunny and smiling nature! 🙂

    #81937

    Hi GraHal yeh good thanks hope you are too (PRT issues aside!) and likewise good to see you’re still soldiering on – been away for a while/threw in the towel about the same time Despair left but drawn back by ‘great ideas for an automated strategy I just gotta try out’ but am again slowly remembering why I left… no doubt I will keep on in the hope that ITF get things sorted out and yeh for sure I know the feeling it’s a difficult enough game as it is eh but at least it all counts towards accumulating knowledge/wisdom… right? (just wish it was more about the markets than the technical issues of a platform!)

    Note: smiling through gritted teeth that is… 😉

    1 user thanked author for this post.
    #81987

    Hey I think I might have sussed out when we get this particular error message?

    If CumulateOrders = False and (for example) the System is Long and conditions are triggered for SellShort then two orders need to be executed …

    • 1 Order to SellShort
      1 Order to Close the Long (because CumulateOrders = False and / or you can’t have opposing positions etc)
    • Order to SellShort gets rejected (because another order (close Long) is in the process of being filled on the same position).
    • Order to Sell Short is executed 1 second later.

     

    Please check out a few of your Rejects for the error message shown attached and say on here if same scenario as the bullet points above (Long / Short could be reversed in your results of course).

    Attached is my evidence.

     

     

    #81994

    Good thinking but the majority of my strategies have always been designed to enter a position then exit (BUY then SELL or SELLSHORT then EXITHSHORT) and wait until conditions are met to enter next trade so am not using opposing order types to close an order although think I did try this in the past and was only today thinking about trying it again as it goes so will post back if unearth anything with the above in mind

    1 user thanked author for this post.
    #82000

    my strategies have always been designed to enter a position then exit (BUY then SELL or SELLSHORT then EXITHSHORT)

    The System I posted screen shots from (2 posts above) is same strategy as you describe above (NOT  opposing orders) but seems that SellShort condition were met / triggered BEFORE the Sell (Exit Long) conditions were triggered.

    May not say much for the strategy (need to analyse further) but it does explain the instances of the error message.

    Same might happen with your Strategies on occasions when you get the Another Order error message?

    #82005

    Ah right ok – but ummmm even if sellshort conditions are met you are already ONMARKET so it should not matter UNTIL the current position has exited assuming you are using IF NOT ON MARKET THEN -> entry conditions – or am I still missing your point?

    That said you are reminding me now that when I screen recorded a strategy running way back with all the charts and open positions windows open to capture everything relevant at the same time and played it back in slow motion/frame by frame there WERE odd things like that going on where the orders seemed to be getting placed the wrong way around if you know what I mean but then reverted to the correct order – I don’t know if that was simply down to PRT messing up displaying what was happening or if it was what was actually happening and was all on the 1 second TF but since that is the lowest TF PRT works in I assume LIMIT and STOP orders on any TF in PRT (ie those orders that do not rely on the close of the previous candle to be executed) ‘operate’ at this TF in order to be sent to and acknowledged by IG hmmmm…. what are we doing… this seems like utter madness spending all this time and going to such great lengths to troubleshoot technical issues on a platform for a company that doesn’t seem to take their clients seriously or at least those clients via IG/do direct ITF clients get better treatment/acknowledgement of their plight with PRT I wonder?

    #82010

    assuming you are using IF NOT ON MARKET THEN

    I just checked and the strategy / screen shots in the link below does not use  IF NOT ON MARKET THEN.
    https://www.prorealcode.com/topic/reject-another-order-same-position/#post-81987

     

    #82014

    Not sure if you are barking up the right tree GraHal as I have seen the message and I have no strategies that SELLSHORT when in a long position.

Viewing 15 posts - 1 through 15 (of 28 total)

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