Bug in ATm strategy chase?

[pjsmith]

Hello,

In 19.1, if you enable 'target chase', which the current describes as so "

4. Target Chase

Enables Auto Chase if touched on your Profit Target orders

"

IF TOUCHED. That's the important bit. Implementing it like that makes perfect sense. BUT, if you enable that option, place an order that gets filled, then targets move towards price even though price has never touched the target. So, either the manual, or the implementation appears incorrect?

[NinjaTrader_ChelseaB]

Hello pjsmith,

I was not able to reproduce that specific behavior, but I think I may be seeing that the chase is not occurring at all with the profit target.

Below is a link to a video.

https://drive.google.com/open?id=1I6PDJ4ueSKUeH_cljYjfRi4aT5zeBdDM

For the behavior you are reporting where the chase is occurring with target without being touched, may I confirm I have taken the correct steps to reproduce?

May I confirm you are using 8.0.19.1?

[pjsmith]

Hi,

Thanks for testing. Yes, I am using 8.0.19.1.

It does not look like the chase was working at all in your video, but I note you did not appear to have the chase limit (t) set. I had mine set to 1 or 2 ticks. When I was testing it the other day, price would move up, price would move down, targets would tick down, all without trade getting anywhere near the target. The only chase option I had enabled was the one you did, 'target chase'.

[NinjaTrader_ChelseaB]

Hello pjsmith,

Thank you for reporting the behavior.

I am looking further into this and will likely be making a report to our development.

I appreciate your patience.

[NinjaTrader_ChelseaB]

Hello pjsmith,

Thanks again for reporting this behavior. I was able to find this behavior is reported and is being tracked with ID# NTEIGHT-13981.

As new releases of NinjaTrader become available, please check the release notes for this ID.

https://ninjatrader.com/support/helpGuides/nt8/release_notes.htm

Once the ID is listed, please update to the latest version and test to confirm the behavior is corrected.

Please let us know of any other behavior you find that you feel is incorrect.