I use a trailing stop SellAtTrailingStop(bar + 1, p, amount, xTrail);When running live, the alert shows a STOP order and stages it instead of a stop loss order. It seems that WL wants me to constantly submit, cancel, and resubmit stop orders while the trade is active. If I edit the order to a stop loss order before submitting it, the alerts continue.

Is this the way it was designed or am I doing something wrong?

One consequence of this is that the strategy and real life get out of sync. That is, I am out of a position with a trailing stop, and WL thinks I am still in the trade. Is there a way to resync during real time trading?

QUOTE:alert shows a STOP order and stages it instead of a stop loss order.

What's the difference? Stop orders are stop orders. They don't know if you're going to lose or not.

Re: TrailingStopamount is the actual stop price. If that price doesn't change, then the orders don't either. If amount is lower than the current trigger price, then nothing changes. However, if amount is higher than the current trigger price, then the order order is canceled and replaced with the new order price.

If you want a fixed stop loss, use either SellAtTrailingStop or SellAtStop, but don't change the trigger price!

A Trailing stop order is triggered by my code.I expect to see a Staged order for a trailing stop which when placed automatically trails the highest price by the set amount.

But this is what appears to be happening:When triggered, the Alert stages a Stop order (not a Trailing Stop) at the target price. As the price moves, Alerts are continually generated and staged for another stop at the new price. Of course I have to cancel the previous stop first.

My question - Is this the way it was designed or am I doing something wrong?

We sent an Verification
Code to your email address. If you don't receive this code within the next 5 minutes.
Please click here to
request a new code.
New Verification Code sent. Please check your Inbox.Please enter your Email to receive a new Verification Code