Account Protector

[mr_ru]

You can tell whether it's netting or hedging by looking at the terminal's window caption:
View attachment 34818

It looks like you are running another EA in your account (fxmon_7.5). And it looks like it is also closing some trades. Could it be that it closes them just before the AP starts closing them?

Thanks for the info, I can confirm all of my accounts are hedging accounts.

FXMON doesn't open/close trades (and in fact I have turned off allow live trading for that EA). It just monitors for things like daily profit, DD, etc.

That said, I do have an EA running on these accounts which open and can close trades if they hit the TP. So you could be right that AP may get triggered by one of the conditions, but when it goes to close the trade the EA has already done it. But I never noticed this being an issue for the last few months that I have been using AP, and I have not changed the EAs I use.

If that is the reason for this, is there any way for me to stop AP spamming the journal/expert/logs if a trade has been closed before AP then tries to close it?

Or is there a way to set the EA that if after 10 attempts for example it stops trying to close that trade so it doesn't spam or some other form of mitigation?
I can't stop using my EAs to trade and be able to close them for me, but I need an account protector like yours which has been amazing so any way to make them both work in tandem? Thanks again mate!

 

[Enivid]

That said, I do have an EA running on these accounts which open and can close trades if they hit the TP. So you could be right that AP may get triggered by one of the conditions, but when it goes to close the trade the EA has already done it. But I never noticed this being an issue for the last few months that I have been using AP, and I have not changed the EAs I use.

I mean, it the AP has its condition triggering - there is floating profit and it reports 5 open positions. According to the logs, it doesn't close any position at all. But you said that it is spamming the line when there are no open positions. That means that the positions have been closed by some other EA.

I will see if I can add some check for excessive close attempts (especially when there are no open positions at all), but I don't know when this will get implemented.

 

[mr_ru]

I mean, it the AP has its condition triggering - there is floating profit and it reports 5 open positions. According to the logs, it doesn't close any position at all. But you said that it is spamming the line when there are no open positions. That means that the positions have been closed by some other EA.

I will see if I can add some check for excessive close attempts (especially when there are no open positions at all), but I don't know when this will get implemented.

Yeah I believe every time I see the logs spammed with that error code there are no positions open whatsoever. And the original EA still opens and closes positions whilst the AP continues to spam the logs. The only way it stops is if I remove the AP EA and then re-add it.

That would be awesome! I think that would be the perfect check, if there are no positions open at all. Okay understood, I guess for now I will remove the AP and try and use a different one until you get around to implementing it. Do you have a rough ETA when I should check back to your website for the updated version? Thanks again for all of the support, I really appreciate it!

 

[Enivid]

Yeah I believe every time I see the logs spammed with that error code there are no positions open whatsoever. And the original EA still opens and closes positions whilst the AP continues to spam the logs. The only way it stops is if I remove the AP EA and then re-add it.

That would be awesome! I think that would be the perfect check, if there are no positions open at all. Okay understood, I guess for now I will remove the AP and try and use a different one until you get around to implementing it. Do you have a rough ETA when I should check back to your website for the updated version? Thanks again for all of the support, I really appreciate it!

Early 2026 is my current best estimate.

 

[mr_ru]

Early 2026 is my current best estimate.

Okay thanks, I look forward to the update! Ru