Rejected / Closed Algos – Error Messages

• 09/17/2021 at 6:24 AM #177753
  GraHal

  We are all frustrated by the many and various Reject Error Messages we get when our Live running Algos are Closed / Rejected.

  This Topic is an attempt to provide a central source of intelligence as to what the Reject Error messages mean and hopefully what – in our  code – has caused the Reject.

  At times it seems that the Reject Error messages are picked at random, almost as though a wheel is spinning and we get whatever error messages the pointer stops on!? 🙂

  So please could we …

  • Try and post error messages exactly as shown in the Yellow Reject Triangle. 
  • Post Screen shot for long error messages as then we capture exact wording (so we don’t confuse PRT Devs etc).
  • Post the reject message shown (under cursor hover) in the Order List where the reject triangle refers us to the Order List for the reason for rejection of out Algo.

  

  GraHal

  Participant

  Topics: 211

  Replies: 8778

  Been thanked: 2183 times
  09/17/2021 at 6:34 AM #177754
  GraHal

  The broker could not confirm status of the last order.

  Surely the last order has either been actioned or rejected, so why the confusion?

  The above error message can appear in the yellow reject triangle and also in the Order List under cursor hover … so are there 2 possible separate problems in the code … any intel any member or PRT please??

  

  GraHal

  Participant

  Topics: 211

  Replies: 8778

  Been thanked: 2183 times
  09/17/2021 at 7:57 AM #177769
  Nicolas

  This happen mostly on demo account, when the broker fail to recognize the order your code is willing to deal with.

  

  Nicolas

  Keymaster

  Topics: 81

  Replies: 20863

  Been thanked: 4773 times
  09/17/2021 at 8:50 AM #177781
  GraHal

  Thank you Nicolas, so what is something we can do in our code to help the broker to recognize the order our code is willing to deal with?

   

  

  GraHal

  Participant

  Topics: 211

  Replies: 8778

  Been thanked: 2183 times
  09/17/2021 at 3:39 PM #177814
  JS

  It seems that the maximum number of pre-loaded bars is limited to 10,000
  When I use an indicator, for example the Standard Deviation, everything goes well up to 10,000 bars and above that I get an error message. (see image)

  Std[10000](close) no error
  Std[10050](close) error

  Std[5050](Close[5050]) error
  Above combination is limited to 5000 bars

  The standard deviation is a recursive calculation so at the start of the system it needs the set bars and when the request is more than 10,000 bars then the system gives an error message.

  

  JS

  Participant

  Topics: 26

  Replies: 1704

  Been thanked: 772 times
  09/17/2021 at 4:50 PM #177818
  GraHal

  Now you know what is causing the problem, are you not able to produce an acceptable / workable Algo with Std using <= 10,000 bars?

   

  

  GraHal

  Participant

  Topics: 211

  Replies: 8778

  Been thanked: 2183 times
  09/17/2021 at 5:44 PM #177819
  JS

  Yes of course I can adjust my algo’s but that is not the way I would like it, because of this limitation I am forced to use a different time scale, etc.

  I thought this topic was meant to collect and describe these kinds of error messages???

  

  JS

  Participant

  Topics: 26

  Replies: 1704

  Been thanked: 772 times
  09/17/2021 at 6:00 PM #177821
  GraHal

  It is, but also describing the result of the limitation (as you have done) is a good thing.

  

  GraHal

  Participant

  Topics: 211

  Replies: 8778

  Been thanked: 2183 times
• Author
  Posts