Announcement

Collapse
No announcement yet.

Partner 728x90

Collapse

ERROR: An Enter() method to submit an entry order at '4/1/2013 7:05:42 PM' has been i

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    ERROR: An Enter() method to submit an entry order at '4/1/2013 7:05:42 PM' has been i

    MarketReplay connection.

    On the previous bar I was short and I issued a BuyToCover -ExitShortLImit() - with a Limitprice = 96.76.
    The limit price was never hit so at the Close Of Bar the ExitShortLimit() order is still working and therefore still Short.

    Now at the CurrentBar I need to go Long using an EnterLongLimit() but I get the above mentioned error message because I think of the following rule:
    Methods that generate orders to enter a position will be ignored if:

    · A position is open and an order submitted by an exit method (ExitLongLimit() for example) is active and the order is used to open a position in the opposite direction

    I should be Flat but I'm not. I am still Short.

    How do I handle this? I think I need to reissue my ExitShortLimit() with a new limit price. There does not seem to be a way to the Limit Price on the still working order because that order is going to be canceled by NT. It seems I need to issue a new ExitShortLimit() and the queue my EnterLongLimt().

    #2
    scjohn, correct the order to reverse would then be ignored in this case in the managed approach - do you send those limits liveUntilCancelled?

    Yes, you would either queue the Long entry to wait until your tightend up ExitShortLimit is filled, or Cancel the working limit via CancelOrder() and then sending the reverse order in OnOrderUpdate() when the cancellation is confirmed. Yet another option would be using a market order in this case, as those would be excluded from the managed mode rules.

    Comment


      #3
      Not using LiveUntilCanceled. Also COBC - true.

      I was a bit surprised to see the OrderStatus still at Waiting at Close Of Bar. Apparently NT had not yet got around to canceling that order. When does NT determine it's time to cancel that or any other order type using the managed approach. I may or may not be issuing a new ExitShortLimit() (in this case).

      It is obvious by the error message that by the time I have issued the EnterLongLimit() order, NT has not gotten around to canceling the ExitShortLimit().

      Comment


        #4
        Thanks scjohn - I would expect the expiration to be done in the next OnBarUpdate() call, so the order would last basically for one bar if not extended through liveUntilCancelled.

        Comment

        Latest Posts

        Collapse

        Topics Statistics Last Post
        Started by Geovanny Suaza, 02-11-2026, 06:32 PM
        0 responses
        647 views
        0 likes
        Last Post Geovanny Suaza  
        Started by Geovanny Suaza, 02-11-2026, 05:51 PM
        0 responses
        368 views
        1 like
        Last Post Geovanny Suaza  
        Started by Mindset, 02-09-2026, 11:44 AM
        0 responses
        108 views
        0 likes
        Last Post Mindset
        by Mindset
         
        Started by Geovanny Suaza, 02-02-2026, 12:30 PM
        0 responses
        571 views
        1 like
        Last Post Geovanny Suaza  
        Started by RFrosty, 01-28-2026, 06:49 PM
        0 responses
        573 views
        1 like
        Last Post RFrosty
        by RFrosty
         
        Working...
        X