Stoploss not put in place

• 12/20/2023 at 1:50 PM #225513
  ashehzi

  SELLSHORT 1.0 CONTRACTS AT myLevel limit SellPrice = TRADEPRICE SET TARGET PLOSS sDistance SET TARGET PPROFIT pDistance

  1 2 3 4

  SELLSHORT 1.0 CONTRACTS AT myLevel limit SellPrice = TRADEPRICE SET TARGET PLOSS sDistance SET TARGET PPROFIT pDistance

  I’ve above code in an algo and short trade just got executed. It set the profit but not stoploss. It has done both in the past so wondering how such msgs between IG and PRT get lost or not fired by PRT. You can see in the attached images.

  

  ashehzi

  Participant

  Topics: 27

  Replies: 85

  Been thanked: 9 times
  12/20/2023 at 2:56 PM #225518
  GraHal

  Does it work correctly with …

  SET Stop PLOSS sDistance

  1	SET Stop PLOSS sDistance

   

  

  GraHal

  Participant

  Topics: 204

  Replies: 8401

  Been thanked: 2042 times
  12/20/2023 at 3:03 PM #225520
  ashehzi

  In general, it works with

  SET TARGET PLOSS sDistance

  I will change to

  SET STOP PLOSS sDistance

  but the same issue can happen randomly. I am not sure if it is related to TARGET instead of STOP but as I said, it works generally.

  

  ashehzi

  Participant

  Topics: 27

  Replies: 85

  Been thanked: 9 times
  12/20/2023 at 5:05 PM #225547
  Jean FX

  I think you could send a technical report to PRT :

  – As soon as you encounter the issue, go to the “Help” menu on the ProRealTime toolbar.
  – Please assure that the window concerned by this issue is open.
  – Click on “Help center”, then on “I have a technical problem”
  – Choose the category “Automatic trading”
  – Give the name of the code you are referring to.
  – To benefit from a technical help, it i necessary to authorize the access to the crypted code. To give them a temporary access, please check the box “I authorize the decryption of the codes (…)”
  – Give as many details as possible, explain the issue you are having in the text box and mention
  – Click “Send report”

  

  Jean FX

  Moderator

  Topics: 0

  Replies: 75

  Been thanked: 18 times
  12/21/2023 at 8:34 AM #225563
  ashehzi

  Is there a way to enable tracing in the product or have a look at the logs without contacting PRT support?

  

  ashehzi

  Participant

  Topics: 27

  Replies: 85

  Been thanked: 9 times
  12/21/2023 at 10:51 AM #225567
  justisan

  hi, I did not know that one can place an order for limiting the losses with a “set target ploss” command, it must be something relatively new. yet I was now opening the programming manual and wow – in fact this possibility is offered.  but I think one needs to read the description very carefully, it tells:

  It is also possible to limit losses with a target order when a position is currently losing. The limit is then placed in the direction of the loss of the position:
  SET TARGET LOSS x: A limit is placed at x units from the position entry price.

  so, it might be very important – that hint to “when a position is currently losing…” – that could mean that corresponding order is issued not at the same time when position is opened, but “later” – at the time when open position runs into losses. I did not test it, it’s only my thinking/guessing.

  1 user thanked author for this post.

  ashehzi

  

  justisan

  Participant

  Topics: 2

  Replies: 73

  Been thanked: 37 times
  12/21/2023 at 10:56 AM #225568
  justisan

  …while with the command “set stop loss” the stop loss order is really always placed at the time of position opening. at least myself I really never experienced a case after (thousands of trades executed) that it was not placed…

  1 user thanked author for this post.

  ashehzi

  

  justisan

  Participant

  Topics: 2

  Replies: 73

  Been thanked: 37 times
  12/21/2023 at 12:03 PM #225572
  ashehzi

  Thanks. I am testing both (SET TARGET PLOSS & SET STOP PLOSS) to see the results.

  

  ashehzi

  Participant

  Topics: 27

  Replies: 85

  Been thanked: 9 times
  12/21/2023 at 4:09 PM #225579
  Wim

  There is also the effect that the LAST “set target x y” cancels the previous “set target a b”. As far as I know it’s always the last “set stop…” or “set target…” that’s active. That explains to me why in your first example the stop wasn’t active (any more).

   

  

  Wim

  Participant

  Topics: 9

  Replies: 78

  Been thanked: 43 times
  12/21/2023 at 5:11 PM #225583
  PeterSt

  Wim wrote:

  As far as I know it’s always the last “set stop…” or “set target…” that’s active.

  Wim, do you mean that a set stop will cancel a set target and vise versa ?
  (this is not really clear and I like to know, not having the experience this time)

  

  PeterSt

  Participant

  Topics: 70

  Replies: 2287

  Been thanked: 695 times
  12/21/2023 at 8:08 PM #225589
  Wim

  Nope. A “set stop” cancels the previous “set stop”, and you need another “set target” to make forget the previous “set target”. It’s like fratricide 🙂

  I almost always use a combination of a set stop and a set target, works flawlessly.

  2 users thanked author for this post.

  ashehzi, PeterSt

  

  Wim

  Participant

  Topics: 9

  Replies: 78

  Been thanked: 43 times
  12/21/2023 at 9:00 PM #225594
  ashehzi

  So you’re telling me below code must leave an order with target profit and stop loss

   

  IF NOT LONGONMARKET AND LongCondition THEN BUY 1.0 CONTRACTS AT myLevel limit SET STOP PLOSS lossDistance SET TARGET PPROFIT profDistance ENDIF

  1 2 3 4 5

  IF NOT LONGONMARKET AND LongCondition THEN BUY 1.0 CONTRACTS AT myLevel limit SET STOP PLOSS lossDistance SET TARGET PPROFIT profDistance ENDIF

  I am not sure it is doing all the time. I am still testing. My understanding any time above code gets executed, it must leave an order with stop loss and target profit limit and should not leave just an order without stop loss and target profit limit because it can adverse effects when the market moves fast.

   

  

  ashehzi

  Participant

  Topics: 27

  Replies: 85

  Been thanked: 9 times
  12/21/2023 at 9:21 PM #225595
  ashehzi

  I’ve below code running since yesterday. It left an order earlier in the day without stop loss and profit:

   

  IF NOT ShortOnMarket AND TIMEOPERATE AND (BARINDEX > 1000) AND (ordersCount < maxOrders) THEN SELLSHORT 1.0 CONTRACTS AT myLevel limit SellPrice = TRADEPRICE SET STOP PLOSS myStopLoss SET TARGET PPROFIT myTargetProfit ENDIF

  1 2 3 4 5 6

  IF NOT ShortOnMarket AND TIMEOPERATE AND (BARINDEX > 1000) AND (ordersCount < maxOrders) THEN SELLSHORT 1.0 CONTRACTS AT myLevel limit SellPrice = TRADEPRICE SET STOP PLOSS myStopLoss SET TARGET PPROFIT myTargetProfit ENDIF

  Please see attached

  

  ashehzi

  Participant

  Topics: 27

  Replies: 85

  Been thanked: 9 times
  12/22/2023 at 12:29 AM #225601
  JS

  According to your screenshots, the order is still “pending”…

  If your order has not been executed, there is no associated Stop Loss and Take Profit…

  I tried your code and after the order was executed, the Stop Loss and Take Profit were immediately placed…

  (Protection Stops and Target orders are linked to an open position and valid until the close of that position)

  

  JS

  Participant

  Topics: 22

  Replies: 1423

  Been thanked: 557 times
  12/22/2023 at 9:21 AM #225607
  ashehzi

  I get your point regarding the sequential nature of the steps. But if I leave a guaranteed order, it shows stop loss and target profit evening in pending state. Same is true for manual order placement but why not for algo order without guaranteed stop. Why it is not an anomaly? It guarantees slippage in news related movement where a second difference between 1st order placement and then stop loss placement can cause big losses.

  

  ashehzi

  Participant

  Topics: 27

  Replies: 85

  Been thanked: 9 times
• Author
  Posts