Mail overloaded

[thecheat]

Hi, I have a strategy that sends email to me every 5 minutes with buy/sell signals. It worked out perfectly before. Today I turned on that strategy again, and it starts to go crazy on me.

The strategy all of sudden start sending out email from historical data. As a result, it rapid fires tons of emails starting from whenever the date begins on my chart until it catches up to the current date.

Is there any internal coding changed in NT's release that causes this problem? Please advise.

[NinjaTrader_Matthew]

Hello thecheat,

Thank you for your post.

There have not been any recent changes that would change the way SendMail() functions.

Have you made any recent changes to your code? Would you be able to provide me with a snippet of the condition that is sending these emails?

[thecheat]

Hi, I can't post all the logic and math of the code because it's too long. However, in essence I have the following logic for sending out mails.

protected override void Initialize()
{

Enabled = true;
ExitOnClose = true;
SyncAccountPosition = true;
CalculateOnBarClose = true;
...........
}

protected override void OnBarUpdate()
{
if (BarsInProgress == 0)
{
// Some math calculation go to here

SendMail("[email protected]","[email protected]", BarsArray[0].Instrument.FullName + " Analysis:" + testReportFive + " (Signal Strength: " + (firstInstFiveFinalBuyRat + firstInstFiveFinalSellRat) + "%)", report);


}

I suspect that this is more have to do with the settings rather than the coding because the coding hasn't been changed since the last time I turned the strategy on and also because the nature of how the emails are based on historical data rather than real time data. Thanks.

[NinjaTrader_Matthew]

thecheat,

Thanks for providing me with this information.

The SendMail() function should only work on real-time data. Are you able to reproduce this issue or was it only this morning you've experienced issues? We will need a reproducible scenario to look into this further.

In addition, I would suggest adding historical checks to your statements to help prevent this from occurring in the future.

if (Historical) return;

[thecheat]

Thank you Matthew, I will give it a shot tonight