Announcement

Collapse
No announcement yet.

Partner 728x90

Collapse

Possible bug.. Reason='Invalid order price, please see log tab'

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

    Possible bug.. Reason='Invalid order price, please see log tab'

    Hi- while I have seen NT7 write to the log when this "'Invalid order price" issue occures using "EnterShortStop" when the condition occurs using "ExitShortStop"
    the trace pickups up on the ignored order, but it is NOT written to the log.

    So in a nut shell, with a invalid order price generated from "ExitShortStop" after NT7 ignores the order, warns of the order being ignored in the trace, it is forgetting to send that warning to the log.

    W2


    #2
    WSquared,

    For information on the price you would want to use TraceOrders = true and read the output from the Output Window. Or you can print your own information via Print().
    Josh P.NinjaTrader Customer Service

    Comment


      #3
      Hi, I should have been more clear. When I don't have trace set to true the "alert" of the ignored order via "EnterShortStop" will be in the log, which I would assume is the proper handling of this issue.

      But in the same strategy run, the log does not recieve the "alert" of ignored orders that were generated via the "ExitShortStop"

      I assume you would want all ignored order warnings to be written to the log (not just those that come from "EnterShortStop") regardless of what trace is set to.

      W2

      Comment


        #4
        WSquared,

        If no message is written it means no issue was ran into. I suggest proper debug tracing to fully understand the price action at time of order submission and the exact order price submitted to get insight into the behavior. Print() will unveil what is happening under the hood.
        Josh P.NinjaTrader Customer Service

        Comment


          #5
          Hi Josh, what I am trying to say is that there was an issue, the order was ignored, but it never was reported to the log that it was ignored.

          W2

          Comment


            #6
            WSquared,

            That is not an issue in itself. Not all ignoral reasons are put into logs. That is what TraceOrders = true is for.

            For example, calling EnterLong() multiple times over and over when you already reached maximum EntriesPerDirection, those additional EnterLong() calls are all ignored, but there are no log messages.
            Josh P.NinjaTrader Customer Service

            Comment


              #7
              Hi Josh, thanks for clearing that up for me.

              W2

              Comment

              Latest Posts

              Collapse

              Topics Statistics Last Post
              Started by Geovanny Suaza, 02-11-2026, 06:32 PM
              0 responses
              633 views
              0 likes
              Last Post Geovanny Suaza  
              Started by Geovanny Suaza, 02-11-2026, 05:51 PM
              0 responses
              364 views
              1 like
              Last Post Geovanny Suaza  
              Started by Mindset, 02-09-2026, 11:44 AM
              0 responses
              105 views
              0 likes
              Last Post Mindset
              by Mindset
               
              Started by Geovanny Suaza, 02-02-2026, 12:30 PM
              0 responses
              567 views
              1 like
              Last Post Geovanny Suaza  
              Started by RFrosty, 01-28-2026, 06:49 PM
              0 responses
              568 views
              1 like
              Last Post RFrosty
              by RFrosty
               
              Working...
              X