Alert Rearm Seconds Not functioning Correctly

[JerryWar]

From Alert Log
CL 09-17 42943.58823 CL TREND LINE TOUCH HIGH @ Time= 14:07:03.414
CL 09-17 42943.58815 CL TREND LINE TOUCH HIGH @ Time= 14:06:55.957
CL 09-17 42943.588 CL TREND LINE TOUCH HIGH @ Time= 14:06:43.417
CL 09-17 42943.58793 CL TREND LINE TOUCH HIGH @ Time= 14:06:36.746
CL 09-17 42943.58792 CL TREND LINE TOUCH HIGH @ Time= 14:06:36.355

Alert Code Rearm is 20 Seconds see code line below.

Alert("TrndLn"+CurrentBar.ToString(), Priority.Medium, MasterName +" TREND LINE TOUCH HIGH @ Time= "+ t.ToString("HH:mm:ss.fff") ,@"C:\Program Files (x86)\NinjaTrader 8\Sounds\"+pSoundFileName,20, Brushes.Transparent, Brushes.Blue );

Play Consecutively is true.
version 8.0.7.1

Jerry

[eDanny]

Are those a rapid succession of bars?

[NinjaTrader_PatrickH]

Hello JerryWar,

Thank you for your post.

The Alert id (string) is different on each bar and therefore is a different alert each time. This means the re-arm is not applicable in this case as each alert is a new id.

Please let me know if you have any questions.

[JerryWar]

Interesting Question, So I looked using the Databox.
Indicator has CalculateOnBarClose = true;
It is a rapid succesion but it is not every bar and
there is one time in there that is not a bar time. Actually in between.
I have had no reloads since so the bars should be the same. ( Volume Bars )

[JerryWar]

LOL - Thanks patrick.
I will change it.

[JerryWar]

Patrick,
Why does the compiler allow for a variable "CurrentBar" in the Tag when there is a value
in ReArm ? Shouldn't they be mutually exclusive ?

[NinjaTrader_PatrickH]

Hello JerryWar,

Thank you for your response.

Anything can technically be used as the id string and those items may update on each bar if you use something like CurrentBar. The Re-Arm should not be restricted if you use CurrentBar because there are use cases in which you may wish to re-arm an alert with a unique id.

Please let me know if you have any questions.